IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-01-24 07:17:08 -06:00
Code Issues Packages Projects Releases Wiki Activity
c45eecad95
grafana/docs/sources/breaking-changes/breaking-changes-v10-3.md
Isabel 2a53ae637e
docs: What’s new & Upgrade guide 10.3 (#80399) 
* initial commit for v10.3 whats new

* Added breaking changes guide and updated What's new doc

* Added 10.2.3 in frontmatter of files

* Added content from What's new in Cloud

* Added note about 10.203 and breaking changes section

* Made formatting edits

* Added 10.2.3 test note

* Replaced 10.2.3 notes with asterisks

* Added tag note

* Move reporting item out of D&V section

* Added breaking changes

* Fixed availability notes

* Moved feature from Traces to Profiles and removed Traces section

* Reordered sections

* Replaced Cloud links with OSS links and relrefs with full URLs

* Updated template

* Copy edit

* Clarified outstanding questions

* Updated data source admin permissions note

* Removed duplicate alerting items

* add InfluxDB SQL support

* Ran prettier

* Added availability, video and contributor info

* Ran prettier

* Added youtube video links

* Removed old video link

---------

Co-authored-by: nmarrs <nathanielmarrs@gmail.com>
Co-authored-by: ismail simsek <ismailsimsek09@gmail.com>
2024-01-22 18:16:26 -05:00

3.9 KiB
Raw Blame History

description keywords labels title weight
Breaking changes for Grafana v10.3
grafana
breaking changes
documentation
10.3
10.2.3
release notes
products
cloud
enterprise
oss
Breaking changes in Grafana v10.3 -2

Breaking changes in Grafana v10.3

Following are breaking changes that you should be aware of when upgrading to Grafana v10.3. Breaking changes that were introduced in release 10.2.3 are also included here and are marked with an asterisk.

For our purposes, a breaking change is any change that requires users or operators to do something. This includes:

  • Changes in one part of the system that could cause other components to fail
  • Deprecations or removal of a feature
  • Changes to an API that could break automation
  • Changes that affect some plugins or functions of Grafana
  • Migrations that can’t be rolled back

For each change, the provided information:

  • Helps you determine if you’re affected
  • Describes the change or relevant background information
  • Guides you in how to mitigate for the change or migrate
  • Provides more learning resources

For release highlights and deprecations, refer to our v10.3 What’s new. For the specific steps we recommend when you upgrade to v10.3, check out our Upgrade guide.

General breaking changes

Transformations*

In panels using the extract fields transformation, where one of the extracted names collides with one of the already existing fields, the extracted field will be renamed. Issue #77569.

If you use the Table visualization, you might see some inconsistencies in your panels. We have updated the table column naming. This will potentially affect field transformations and/or field overrides. To resolve this, either:

  • Update the transformation you are using
  • Update field override. Issue #76899.

Users who have transformations with the Time field might see their transformations are not working. Those panels that have broken transformations will fail to render. This is because we changed the field key. See related PR: #69865. To resolve this, either:

  • Remove the affected panel and re-create it
  • Select the Time field again
  • Edit the time field as Time for transformation in panel.json or dashboard.json. Issue #76641.

Data source permissions*

The following data source permission endpoints have been removed:

  • GET /datasources/:datasourceId/permissions
  • POST /api/datasources/:datasourceId/permissions
  • DELETE /datasources/:datasourceId/permissions
  • POST /datasources/:datasourceId/enable-permissions
  • POST /datasources/:datasourceId/disable-permissions

Please use the following endpoints instead:

  • GET /api/access-control/datasources/:uid for listing data source permissions
  • POST /api/access-control/datasources/:uid/users/:id, POST /api/access-control/datasources/:uid/teams/:id, and POST /api/access-control/datasources/:uid/buildInRoles/:id for adding or removing data source permissions

If you are using the Grafana provider for Terraform to manage data source permissions, you will need to upgrade your provider to version 2.6.0 or newer to ensure that data source permission provisioning keeps working. Issue #5880.