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.
AGPL-3.0 License
Bot releases are visible (Hide)
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 4 months ago
Download page
What's new highlights
/_mapping
requests. #87711, @svennergr
Published by grafana-delivery-bot[bot] 4 months ago
Published by grafana-delivery-bot[bot] 4 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 4 months ago
Download page
What's new highlights
If you had selected your language as "Português Brasileiro" previously, this will be reset. You have to select it again in your Preferences for the fix to be applied and the translations will then be shown. Issue #89374
Published by grafana-delivery-bot[bot] 4 months ago
Download page
What's new highlights
maxWidth
option. #88652, @adela-almasan
plugin.json
schema with UI extensions meta-data. #88288, @leventebalogh
__alert_rule_uid__
and move into drawer. #87320, @tomratcliffe
plugin.json
schema. #86520, @leventebalogh
X-Scope-OrgID
and tenant IDs. #85726, @fabrizio-grafana
joinByField
transformation. #87409, @baldm0mma
/alertmanager
when sending alerts to mimir targets if not already present. #85543, @alexweav
Users that provision alert rules into folders whose titles contain slashes from now on they should escape them:
eg. if an alert group contains:
folder: folder_with_/_in_title
it should become:
folder: folder_with_\/_in_title
Issue #77450
The grafana.explore.richHistory.activeDatasourceOnly
local storage key is deprecated, and will be removed in Grafana 12. You may experience loss of your Explore query history or autocomplete data if you upgrade to Grafana 12 under 2 weeks of Grafana 11.1. Actual risk of data loss depends on your query history retention policy. Issue #86250
Select
group headers to always be visible. #88178, @ashharrison90
tabular
prop to Text component for tabular numbers. #87440, @JoaoSilvaGrafana
Published by grafana-delivery-bot[bot] 4 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
res
being accessed after it becomes nil
in promql_query.go
. #85959, @adamyeats
auto
refresh option when saving a dashboard. #85921, @bfmatei
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 5 months ago
Download page
What's new highlights
SQL_VARIANT
converter and update test. #86469, @aangelisc
cloudMonitoringProm.run
. #85928, @adamyeats
auto
refresh option when saving a dashboard. #85922, @bfmatei
The @grafana/e2e
package is deprecated in Grafana 11.0.0. If your Grafana plugin has end-to-end tests that use @grafana/e2e
, it's recommended to replace them with @grafana/plugin-e2e
and Playwright. For information on how to migrate, please refer to the plugin-e2e docs. Issue #85778
Published by grafana-delivery-bot[bot] 6 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 6 months ago
Download page
What's new highlights
oauth_skip_org_role_update_sync
as an option. #84972, @eleijonmarck
pluginsDynamicAngularDetectionPatterns
by default. #84723, @xnyo
enablePluginsTracingByDefault
by default. #84645, @xnyo
query
option from splitOpen
. #83973, @Elfo404
never
to further discourage. #83681, @joshhunt
res
being accessed after it becomes nil
in promql_query.go
. #84223, @adamyeats
In 9.3 we released a way to set case_insensitive_login
to true. This enables, lowercased username, login for users signing up with Grafana, for more information read our blog post.
If you encounter any issues with users signing up, we recommend everyone to use lowercase in their login, username otherwise refer to the blog post for how to solve any of the users that can be conflicting with their login/username. Issue #84972
This is a breaking change for users who use uppercase in their login or emails. The users are by default now using lowercase as part of their login and emails.
Before this code change, users would be able to still log in as either [email protected]
or [email protected]
, users are now only able to login and signup with grafana using lowercasing [email protected]
.
We recommend reviewing the blog post about using the CLI and why this is important for us to consolidate our security efforts. Issue #84840
This is a breaking change for users who have restricted the default access to annotation permissions by removing annotation related actions from the Viewer or Editor basic roles. In such cases we are not able to complete the permission migration automatically, and you will see the following log in your Grafana server logs: basic role permissions missing annotation permissions, skipping annotation permission migration
. You will also notice that dashboard and folder permissions do not appear in the user interface. Don't worry, all the permissions that you assigned are still there, they are just not being displayed.
We recommend reviewing what annotation permissions you have revoked from the basic roles (you can reference our documentation to see what permissions are missing). If you are fine granting them back to the basic roles, do that, then run the following data base command: DELETE FROM migration_log WHERE migration_id="managed dashboard permissions annotation actions migration"
and restart Grafana. This will make sure that the annotation permission migration gets run again, and this time it should succeed.
If you are not willing to grant the annotation permissions back to the basic roles, please disable annotationPermissionUpdate
feature toggle (add annotationPermissionUpdate = false
to [feature_toggles]
in Grafana's configuration file) and reach out to Grafana's support team. When we can learn more about your use case, we will work with you to find a solution. Issue #84787
Angular support is turned off
by default starting Grafana 11, you can find all the details in a dedicated documentation page.
Special notes for your reviewer:
Please check that:
The xpack checkbox dependency for enabling the Include Frozen Indices functionality has been removed, allowing direct control over frozen indices inclusion. Users should review their datasource settings to ensure the "Include Frozen Indices" option is configured as desired, particularly if xpack was previously disabled. This change aims to simplify configuration options and may affect queries if settings are not adjusted accordingly. Issue #84734
For data sources that extend DataSourceWithBackend
, the filterQuery
method is now called before the data source query
method. If the filterQuery
method assumes that some kind of query migration happens before this method is called, you now need to do the migration inside this method.
Users of data source plugins that did not previously remove hidden queries will see a change of behaviour: Before this change, clicking the Disable query
button had no impact on the query result, but starting from Grafana 11 responses associated with hidden queries will no longer be returned to the panel. Issue #84656
SystemJS is no longer exported from @grafana/runtime
. Plugin developers should instead rely on importing modules / packages using standard TS import syntax and npm/yarn for package installation.
Please check that:
We've removed the Loki tab from the Tempo data source. You can still access Logs through the Loki data source or can also create a link from Tempo to Loki via our trace to logs feature. Issue #84346
The query
option in splitOpen
was deprecated in 10.1
and is now being removed. Issue #83973
Since https://github.com/grafana/grafana/pull/38942 (Grafana 8.2.0
) the ExploreQueryFieldProps
type was deprecated and is now removed. Issue #83972
Since https://github.com/grafana/grafana/pull/38942 exploreId
is no longer supplied to query editors in Explore. The property was deprecated in 10.3.0
and is now removed. If your query editor needs to know from which app is being rendered, you can check the app
prop in QueryEditorProps
. Issue #83971
The Vector interface that was deprecated in Grafana 10 has been further deprecated. Using it will now generate build-time Typescript errors, but remain working at runtime. If you're still using ArrayVector in your code, it should be removed immediately and replaced with plain arrays. Plugins compiled against older versions and depend on calling get/set will continue to work because the Array prototype still has a modified prototype. This will be removed in the future Issue #83681
In Grafana 11 the legacy alerting reaches the end-of-life. Users cannot enable it and Grafana will refuse to start if the settings are not updated to run the new Grafana Alerting. Migration from legacy alerting is not available as well. Grafana 10.4.x is the last version that offers the migration.
If the setting [alerting].enable
is set to true
Grafana will not start and emit the log message with recommendations to change the configuration
Setting [alerting].max_annotation_age
is replaced by [unified_alerting.state_history.annotations].max_age
Setting [alerting].max_annotations_to_keep
is replaced by [unified_alerting.state_history.annotations].max_annotations_to_keep
setting [unified_alerting].execute_alerts
does not fall back to the legacy [alerting].execute_alerts
anymore. Instead, the default value true
is used.
setting [unified_alerting].evaluation_timeout
does not fall back to the legacy setting [alerting].evaluation_timeout_seconds
in the case when it is either invalid or has the default value. Now, if the setting is invalid, it will cause Grafana to exit.
setting [unified_alerting].min_interval
does not fall back to the legacy setting [alerting].min_interval_seconds
in the case when it is either invalid or has the default value. Now, if the setting is invalid, it will cause Grafana to exit. Issue #83651
We've removed React 17 as a peer dependency from our packages. Anyone using the new versions of these packages should ensure they've upgraded to React 18 following the upgrade steps: https://react.dev/blog/2022/03/08/react-18-upgrade-guide Issue #83524
We're adding a validation between the response of the ID token HD parameter and the list of allowed domains as an extra layer of security. In the event that the HD parameter doesn't match the list of allowed domains, we're denying access to Grafana.
If you set Google OAuth configuration using api_url,
you might be using the legacy implementation of OAuth, which doesn't have the HD parameter describing the organisation the approved token comes from. This could break your login flow.
This feature can be turned off through the configuration toggle validate_hd
. Anyone using the legacy Google OAuth configuration should turn off this validation if the ID Token response doesn't have the HD parameter. Issue #83229
The direct input datasource plugin has been removed in Grafana 11. It has been in alpha for 4 years and is superseded by TestData that ships with Grafana.
Please check that:
The alert rule API methods now require more permissions for users to perform changes to rules. To create a new rule or update or delete an existing one, the user must have permission to read from the folder that stores the rules (i.e. permission folder:read
in the scope of the rule's folder) and permission to read alert rules in that folder (i.e. permission alert.rules:read
The standard roles already have all required permissions, and therefore, neither OSS nor Grafana Enterprise users who use the fixed roles (standard roles provided by Grafana) are affected. Only Grafana Enterprise users who create custom roles can be affected Issue #78289
The deprecated endpoint for rendering pdf of a single dashboard GET /render/pdf/:dashboardID
and report model fields dashboardId
, dashboardName
, dashboardUid
, and templateVars
have been removed. Only new endpoint GET /api/reports/render/pdfs
accepting dashboards
list is support moving forward Issue #6362
The deprecated old schedule setting with separate fields hour,
minute
, day
have been removed. Only new schedule setting with startDate
will be supported moving forward Issue #6329
The deprecated email
field to send a report via /api/reports/email
endpoint have been removed. Only emails
field will be supported moving forward. Issue #6328
Published by grafana-delivery-bot[bot] 7 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 7 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 7 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 7 months ago
Download page
What's new highlights
Published by grafana-delivery-bot[bot] 7 months ago
Download page
What's new highlights