apitech
/
grafana
mirror of https://github.com/grafana/grafana
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
59649 Commits
2179 Branches
608 Tags
1.9 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 106188-alerting-docs-best-practices-edit
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '106188-alerting-docs-best-practices-edit'
${ noResults }
grafana/docs/sources/breaking-changes/_index.md

1.2 KiB
Raw Permalink Blame History

aliases description labels title weight
[guides/] Learn about breaking changes in Grafana [{products [cloud enterprise oss]}] Breaking changes 2

Breaking changes in Grafana

In some cases, major releases that introduce many new features also introduce breaking changes. These changes are described, along with information about what to do, in the breaking changes pages specific to each release.

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

{{% admonition type="note" %}}

To learn what's available in a Grafana release, refer to the What's new page for each version. For the steps we recommend when you upgrade, check out the Upgrade guide for each version.

{{% /admonition %}}

Refer to any of the following breaking changes guides:

{{< section menuTitle="true">}}