mirror of https://github.com/grafana/grafana
Docs: Add What's New in Grafana v9.2 Beta (#55855)
parent
97f1524b66
commit
3409979288
@ -0,0 +1,213 @@ |
||||
--- |
||||
_build: |
||||
list: false |
||||
aliases: |
||||
- /docs/grafana/latest/guides/whats-new-in-v9-2/ |
||||
description: Feature and improvement highlights for Grafana v9.2 |
||||
keywords: |
||||
- grafana |
||||
- new |
||||
- documentation |
||||
- '9.2' |
||||
- release notes |
||||
title: What's new in Grafana v9.2 |
||||
weight: -33 |
||||
--- |
||||
|
||||
# What's new in Grafana v9.2 (Beta) |
||||
|
||||
Welcome to Grafana v9.2, a hefty minor release with a swath of improvements that help you create and share dashboards and alerts. |
||||
Read on to learn about progress on public dashboards, our new panel help menu, custom branding in Grafana Enterprise, and improvements to access control. |
||||
If you'd prefer to dig into the details, check out the complete [changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). |
||||
|
||||
## Panel help menu |
||||
|
||||
_Available in beta in Grafana Open Source._ |
||||
|
||||
Dashboard panel issues can occur for all kinds of reasons, from problems processing data to issues with rendering or configuration. |
||||
Shorten your communication time when reporting issues and requesting help from Grafana Labs by grabbing a panel's query response data and panel settings. |
||||
This will help the support team reproduce, diagnose, and fix the issue as quickly as possible. |
||||
See our [documentation](https://grafana.com/docs/grafana/latest/troubleshooting/send-panel-to-grafana-support/) for more info. |
||||
|
||||
For details, see [GitHub issue #55005](https://github.com/grafana/grafana/issues/55005) and ["Send a panel to Grafana Labs support"](https://grafana.com/docs/grafana/latest/troubleshooting/send-panel-to-grafana-support/) in the documentation. |
||||
|
||||
Screenshot |
||||
|
||||
## Support for Google Analytics 4 properties |
||||
|
||||
_Generally available in Grafana Open Source._ |
||||
|
||||
You can now use Google Analytics 4 (GA4) to track usage of Grafana. |
||||
To enable tracking with GA4, specify your property's measurement ID in Grafana's configuration file. |
||||
Read more [in our documentation](https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#google_analytics_4_id). |
||||
|
||||
Google Analytics 4 replaces Universal Analytics, which will stop processing hits in 2023 (July 1 for free accounts, October 1 for Google Analytics 360). |
||||
You can continue using Universal Analytics with Grafana and send analytics data to both types of properties. |
||||
|
||||
## Alertmanager updated to be based on Prometheus Alertmanager v0.24 |
||||
|
||||
_Generally available in all editions._ |
||||
|
||||
The Alertmanager used for Grafana-managed alert rules is now based on the latest release of the Prometheus Alertmanager, v0.24. |
||||
We continue to unify the different Alertmanagers that you can use with Grafana Alertmanager and will provide updates on this topic in a future release of Grafana. |
||||
|
||||
For details, see [GitHub pull request #53555](https://github.com/grafana/grafana/pull/53555). |
||||
|
||||
## Grafana Alerting alert rules now return an Error state by default on execution error or timeout |
||||
|
||||
_Generally available in all editions._ |
||||
|
||||
Error rules created with Grafana Alerting were previously switching to an Alerting state when the rule was facing an execution error or timeout. |
||||
New error rules now switch by default to the `Error` state when failing to execute or timing out. |
||||
You can change this default to either `Alerting` or `OK`. |
||||
|
||||
This change does not update existing alert rules. |
||||
|
||||
For details on this change, see [GitHub pull request #55345](https://github.com/grafana/grafana/pull/55345). |
||||
For more information about alerting states, see the [alerting documentation](https://grafana.com/docs/grafana/latest/alerting/fundamentals/state-and-health/). |
||||
|
||||
## Public dashboards |
||||
|
||||
_Available in Experimental in Grafana Open Source, Enterprise, Cloud Pro, and Cloud Advanced._ |
||||
_To enable public dashboards, you must enable a feature flag or request this feature from support._ |
||||
|
||||
[Public dashboards](https://grafana.com/docs/grafana/latest/dashboards/dashboard-public/) launched as an experimental feature in Grafana v9.1. |
||||
We've received lots of great feedback on this much-anticipated feature and thank everyone who has helped us improve it. |
||||
The team has been hard at work polishing public dashboards, and we've closed quite a few bugs related to community reports. |
||||
If you're trying out public dashboards, let us know how it is going in the [open discussion in GitHub](https://github.com/grafana/grafana/discussions/49253). |
||||
Beyond bug fixes, we're excited to share some new features: |
||||
|
||||
### Expression support |
||||
|
||||
We have added the ability to use [expressions](https://grafana.com/docs/grafana/latest/panels/query-a-data-source/use-expressions-to-manipulate-data/about-expressions/) for your public dashboards. |
||||
|
||||
Screenshot |
||||
|
||||
### Public dashboard usage insights |
||||
|
||||
_Available in Experimental in Grafana Enterprise._ |
||||
|
||||
Usage Insights now has a "Public Dashboards" tab, which tracks how many people are viewing your public dashboard and how many queries have ran, and counts errors. |
||||
|
||||
Screenshot |
||||
|
||||
### Use RBAC to allow any user to share dashboards publicly |
||||
|
||||
_RBAC is available in Grafana Enterprise and Cloud Advanced._ |
||||
|
||||
We have introduced a new role called "Public Dashboard writer" that grants access to publish new public dashboards to additional roles and users. |
||||
By default, only admins can share dashboards publicly. |
||||
|
||||
Screenshot |
||||
|
||||
## Revamped UI for Google Cloud monitoring |
||||
|
||||
_Generally available in Grafana Open Source and Grafana Cloud Free, Pro, and Advanced._ |
||||
|
||||
The Google Cloud monitoring data source UI has been brought up to date with the latest Grafana UI design. |
||||
This new interface provides a more consistent experience as you switch between different data sources. |
||||
It also groups query builder items together more logically, so it's easier to write queries. |
||||
In the case of Cloud monitoring, the query builder's groupings should more closely match the groupings in Google's Cloud console. |
||||
|
||||
Screenshot |
||||
|
||||
## App Plugins: better handling for secure fields |
||||
|
||||
Plugin developers can mark certain fields as secure to encrypt those fields in Grafana's database. |
||||
This is important for sensitive fields like data source passwords or API keys. |
||||
Previously, plugin developers needed to manually track which fields were labeled secure. |
||||
We have extended our plugins platform to simplify this, which means one less thing for developers to worry about and better security for all users' data. |
||||
For details on using this functionality, see [GitHub pull request #55313](https://github.com/grafana/grafana/pull/55313) and our [plugin examples](https://github.com/grafana/grafana-plugin-examples) repository. |
||||
|
||||
## Transformations: outer joins and bug fixes |
||||
|
||||
Transformations allow you to shape raw data from data sources, like metrics series or GitHub issues, so that you can visualize them as clearly as possible. |
||||
We have extended the Join transformation to support both inner and outer JOINs, which work similarly to SQL inner and outer JOINs. |
||||
|
||||
Also, you can now click on the `x` to clear values in the select fields for the Outer Join and Grouping to Matrix transformations as expected. |
||||
|
||||
Screenshot |
||||
|
||||
## Custom branding previews |
||||
|
||||
_Available in beta in Grafana Enterprise._ |
||||
|
||||
Use custom branding to make Grafana _your_ observability tool by adding your own sign-in page, docs and help links, logo, application name, and more. |
||||
Previously, you could configure custom branding only in Grafana's configuration files. |
||||
In Grafana v9.1, we introduced a UI where you can update and upload content. |
||||
In v9.2, you can preview what your customized Grafana will look like on the custom branding page before applying your changes. |
||||
|
||||
Turn on the custom branding configuration page and API with the `customBranding` [feature toggle](https://grafana.com/docs/grafana/latest/packages_api/data/featuretoggles/), and learn more about what you can do with custom branding in our [documentation](https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/configure-custom-branding/). |
||||
|
||||
Screenshot |
||||
|
||||
## Simplified UI to create template variable queries for Loki data source |
||||
|
||||
_Generally available in Grafana Open Source._ |
||||
|
||||
We have significantly simplified and improved the way you can create template variable queries for Loki data sources in dashboards. |
||||
Use drop-downs to choose query type, label, and stream selector, without needing to worry about templating query syntax. |
||||
For more information, refer to [Loki data source documentation](https://grafana.com/docs/grafana/latest/datasources/loki/#query-variable). |
||||
|
||||
Screenshot |
||||
|
||||
## Authentication and authorization |
||||
|
||||
### Teams can be empty or without any Admin user |
||||
|
||||
_Generally available in all editions._ |
||||
|
||||
You can now leave a team empty without any users, or have only Members in a team. |
||||
This helps you sync teams and users from a single sign-on provider like Active Directory or Okta, or if you use teams as collections of permissions. |
||||
Previously, teams required at least one Admin user to be in a team. |
||||
|
||||
Screenshot |
||||
|
||||
### Role-based access control is easier to use |
||||
|
||||
_Generally available in Grafana Enterprise and Grafana Cloud Advanced._ |
||||
|
||||
#### Role picker when creating and editing teams |
||||
|
||||
You can now choose a team's roles and permissions when creating a new team or editing an existing team, which helps you grant permissions to teams more efficiently. |
||||
Previously, you could assign roles only when looking at a list of all teams. |
||||
|
||||
Screenshot |
||||
|
||||
#### RBAC: Organize custom roles into groups |
||||
|
||||
If you create many custom roles in Grafana – for example, different roles for editing specific dashboards or folders, or specific roles for certain teams in your company – you can now organize them into groups for more efficient navigation, browsing, and custom role assignment. |
||||
For more information on custom roles, see the [documentation](https://grafana.com/docs/grafana/latest/developers/http_api/access_control/#create-a-new-custom-role). |
||||
|
||||
Screenshot |
||||
|
||||
#### RBAC: Terraform resource for assigning fixed and custom roles to users, teams, and service accounts |
||||
|
||||
You can now assign fixed and custom roles to users, teams, and service accounts with the Grafana role_assignment resource in Terraform. |
||||
This allows you to provision user permissions in a version-able, repeatable way if you use Terraform. |
||||
Learn more in the [documentation](https://registry.terraform.io/providers/grafana/grafana/latest/docs/resources/role_assignment) for Grafana's Terraform provider. |
||||
|
||||
## SAML role mapping improvements |
||||
|
||||
_Generally available in Grafana Enterprise, Grafana Cloud Pro, and Advanced._ |
||||
|
||||
### Map a user to all organizations in Grafana |
||||
|
||||
You can now use `*` as the Grafana organization in the mapping to add all users from a given SAML Organization to all existing Grafana organizations. |
||||
For more information, see ["Configure SAML authentication"](https://grafana.com/docs/grafana/next/setup-grafana/configure-security/configure-authentication/saml/#configure-organization-mapping) in the documentation. |
||||
|
||||
### Skip organization role sync |
||||
|
||||
Generally available in Grafana Enterprise, Grafana Cloud Pro, and Advanced. |
||||
|
||||
If you use a SAML identity provider to manage your users but prefer to assign roles and permissions in the Grafana UI or via API, you can now enable a configuration option to skip user organization and roles synchronization with your SAML provider. |
||||
|
||||
Use the `skip_org_role_sync` configuration option when configuring SAML to prevent synchronization with SAML roles and make user roles editable from within Grafana. |
||||
|
||||
For more information, see the [SAML configuration documentation](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/saml/). |
||||
|
||||
## Assign Server Admin permissions from Oauth |
||||
|
||||
You can now map OAuth groups and roles to Server Admin for the GitLab, GitHub, AzureAD, Okta, and Generic OAuth integrations. |
||||
To enable this functionality, set the `allow_assign_grafana_admin` configuration option to `true` in the desired OAuth integration section. |
||||
For more information, see the [authentication configuration documentation](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/) for each OAuth client. |
Loading…
Reference in new issue