Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
kind
,attribute
andidentifier
fields for better search performance. #71933, @IevaVasiljevaNew folder
into a drawer. #69706, @ashharrison90decolorize
logql operation. #68972, @ivanahuckovaSkip to content
link. #68065, @ashharrison90$__timezone
template variable. #66785, @VictorColombBug fixes
serviceTags
andtags
to be empty for trace results. #73197, @aangeliscNew dashboard
page has the correct breadcrumb hierarchy. #69758, @ashharrison90skip_org_role_sync
with Env variables. #68364, @eleijonmarckBreaking changes
This change impacts all instances that use external authentication providers to manage users and organization role assignments.
From Grafana 10.1, it will no longer be possible to manually update organization roles (Viewer, Editor and Admin) that are managed by an external auth provider. We are making this change to clearly separate between roles managed by an external auth provider and manually assigned roles, which increases security and clarity around role management.
If you prefer to manually set user organization roles, use
skip_org_role_sync
option in the Grafana configuration file of your OAuth provider.Refer to the release notes of Grafana 9.5 for context on the previous work done to build up to this change. Issue #72204
This change impacts GitHub OAuth, Gitlab OAuth, Okta OAuth and Generic OAuth
Currently if no organization role mapping is found for a user when connecting via OAuth, Grafana doesn’t update the user’s organization role.
With Grafana 10.1, on every login, if the role_attribute_path property does not return a role, then the user is assigned the role specified by the auto_assign_org_role option.
To avoid overriding manually set roles, enable the
skip_org_role_sync
option in the Grafana configuration for your OAuth provider. Issue #70766InfluxDB backend parser returns incompatible data with frontend. The data was being parsed by frontend and we moving towards migrating InfluxDB fully backend. One caveat is Frontend is generating data frames with fields
Time
andValue
. The backend parser, however, generatestime
andvalue
. This is causing issues and inconsistencies for the features (i.e. transformations) relying on those. In order to have a unique approach we choose to support what most of the users already have. Existing Transformations that depend ontime
fields have to be updated to useTime
fields. Issue #69865For accessibility reasons
tooltip
oraria-label
are now required properties forIconButton
. In order to continue to useIconButton
, you must ensure allIconButton
components have a corresponding tooltip or aria-label text. The tooltip text will also be used as the aria-label if you didn't set one separately. In case you add an aria-label the IconButton will not show a tooltip. Issue #69699The implementation for template macro
${__series.name}
was not always correct, resulting in an interpolation that was very different from the series name displayed in the visualization. We have now fixed this issue so that it does show the same name. Depending on how${__series.name}
is used this could result in a minor breaking change. Issue #69621The data source template variable type has changed the way it represents its options. The
text
field still represents the data source name, but thevalue
has been changed to theuid
of the data source. This allows dashboards to declare the currently selected option byuid
, however it changes how a datasource template variable value will be rendered by default. If the name of the data source is expected, the variable syntax will have to be changed to specify the text format.For example, given a data source variable (datasourceVariable), the following string:
was previously interpolated as:
After these changes, it's interpolated as:
Any dashboards that are relying on the data source name being returned by
${datasourceVariable}
will have to update all their usages to${datasourceVariable:text}
in order to get the previous behavior.Affected use cases:
${datasourceVariable}
to display the data source name in text panel or in the panel title.${datasourceVariable}
to use the data source name as part of the query content.Unaffected use cases:
${datasourceVariable}
to choose which data source to use for a query (through its data source picker) will not be affected since it can use both the name and the uid Issue #69259We are changing the logic that creates
uid
inLogRowModel
. Previously, foruid
we usedid
field from log's data frame. Unfortunately, when users run multiple queries that returned duplicate logs data,uid
was not unique which was causing bugs. To makeuid
unique across multiple queries that return duplicate logs data, we are now prependinguid
withrefId
of query that produced the log line. We recommend not to rely onLogRowModel
uid
and instead usedataFrame
id
field. Issue #68569The deprecated support for monitoring Grafana frontend using Sentry javascript agent has been removed in this release. If you have frontend logging enabled and are sending telemetry to Sentry by setting
sentry_dsn
configuration property, this will no longer work. Otherwise, if frontend logging is enabled, it will now automatically use Grafana Faro agent. Issue #67493Deprecations
The query parameter of Explore's
SplitOpen
function is deprecated (passed inmapInternalLinkToExplore
). Please use thequeries
parameter instead, which allows passing multiple queries toSplitOpen
function. To pass a single query toSplitOpen
function, set thequeries
parameter to an array containing that single query.Fixes: grafana/grafana#62567 Issue #71484
Starting with 10.0, changing the folder UID is deprecated. It will be removed in a future release. Please avoid using it because it can result in folder losing its permissions. Issue #68543
Plugin development fixes & changes