grafana

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

Downloads
680.2K
Stars
60.2K
Committers
2.4K

Bot releases are visible (Hide)

grafana - 8.5.9 (2022-07-14)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Bug fixes

  • Security: Fixes for CVE-2022-31107 and CVE-2022-31097. #52238, @xlson
grafana - 8.4.10 (2022-07-14)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Bug fixes

grafana - 9.0.2 (2022-06-28)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

Bug fixes

grafana - 9.0.1 (2022-06-21)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Alerting: Add support for image annotation in Alertmanager alerts. #50686, @grobinson-grafana
  • Alerting: Add support for images in SensuGo alerts. #50718, @grobinson-grafana
  • Alerting: Add support for images in Threema alerts. #50734, @grobinson-grafana
  • Alerting: Adds Mimir to Alertmanager data source implementation. #50943, @gillesdemey
  • Alerting: Invalid setting of enabled for unified alerting should return error. #49876, @grobinson-grafana
  • AzureMonitor: Clean namespace when changing the resource. #50311, @andresmgot
  • AzureMonitor: Update supported namespaces and filter resources by the right type. #50788, @andresmgot
  • CLI: Allow relative symlinks in zip archives when installing plugins. #50537, @marefr
  • Dashboard: Don't show unsaved changes modal for automatic schema changes. #50822, @torkelo
  • Dashboard: Unsaved changes warning should not trigger when only pluginVersion has changed. #50677, @torkelo
  • Expression: Execute hidden expressions. #50636, @yesoreyeram
  • Geomap: Support showing tooltip content on click (not just hover). #50985, @ryantxu
  • Heatmap: Remove alpha flag from new heatmap panel. #50733, @ryantxu
  • Instrumentation: Define handlers for requests that are not handled with named handlers. #50613, @bergquist
  • Log Panel: Improve log row hover contrast and visibility. #50908, @Seyaji
  • Logs: Handle backend-mode errors in histogram. #50535, @gabor
  • Loki: Do not show histogram for instant queries. #50711, @gabor
  • Loki: Handle data source configs with path in the url. #50971, @gabor
  • Loki: Handle invalid query type values. #50755, @gabor
  • OAuth: Redirect to login if no oauth module is found or if module is not configured. #50661, @kalleep
  • OptionsUI: Move internal options editors out of @grafana/ui. #50739, @ryantxu
  • Prometheus: Don't show undefined for step in collapsed options in query editor when value is "auto". #50511, @aocenas
  • Prometheus: Show query patterns in all editor modes for Prometheus and Loki. #50263, @ivanahuckova
  • Tempo: Add link to Tempo Search with node service selected. #49776, @joey-grafana
  • Time Series Panel: Add Null Filling and "No Value" Support. #50907, @codeincarnate
  • TimeSeries: Add an option to set legend width. #49126, @bobrik
  • Timeseries: Improve cursor Y sync behavior. #50740, @ryantxu
  • Traces: Do not use red in span colors as this looks like an error. #50074, @joey-grafana

Bug fixes

Deprecations

Support for compact Explore URLs is deprecated and will be removed in a future release. Until then, when navigating to Explore using the deprecated format the URLs are automatically converted. If you have existing links pointing to Explore update them using the format generated by Explore upon navigation.

You can identify a compact URL by its format. Compact URLs have the left (and optionally right) url parameter as an array of strings, for example &left=["now-1h","now"...]. The standard explore URLs follow a key/value pattern, for example &left={"datasource":"test"...}. Please be sure to check your dashboards for any hardcoded links to Explore and update them to the standard URL pattern. Issue #50873

grafana - 8.5.6 (2022-06-14)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Bug fixes

  • Dashboard: Fixes random scrolling on time range change. #50379, @torkelo
  • Security: Fixes minor code scanning security warnings in old vendored javascript libs. #50382, @torkelo
grafana - 9.0.0 (2022-06-14)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

Bug fixes

  • Alerting: Fix database unavailable removes rules from scheduler. #49874, @grobinson-grafana
  • AzureMonitor: Fix auto-selection of time-grain for metrics. #49278, @aangelisc
  • DataSources: Fixes issue with expressions not being queried. #50446, @JoaoSilvaGrafana
  • GraphNG: Fix thresholds by color not following data update. #48571, @zoltanbedi
  • Jaeger: Update operations dropdown. #49329, @joey-grafana
  • Login: Fix mismatching label on auth_module in user list. #49177, @Jguer
  • Playlists: Save button now correctly creates a new playlist. #50381, @ashharrison90
  • RBAC: Fix migrations running in the wrong order causing inheritance problem in enterprise. #50452, @gamab
  • RBAC: Fix migrations running into the wrong order. (Enterprise)
  • ServiceAccounts: Add identifiable token prefix to service account tokens. #49011, @Jguer
  • Traces: Fix missing CopyButton on KeyValueTables and overlapping of panels. #49271, @svennergr

Breaking changes

The @grafana/ui package helper function selectOptionInTest used in frontend tests has been removed as it caused testing libraries to be bundled in the production code of Grafana. If you were using this helper function in your tests please update your code accordingly:

// before
import { selectOptionInTest } from '@grafana/ui';
// ...test usage
await selectOptionInTest(selectEl, 'Option 2');

// after
import { select } from 'react-select-event';
// ...test usage
await select(selectEl, 'Option 2', { container: document.body });

Issue #50442

Removed deprecated checkHealth prop from the @grafana/e2e addDataSource config. Previously this value defaulted to false, and has not been used in end-to-end tests since Grafana 8.0.3. Issue #50296

Removes the deprecated LegacyBaseMap, LegacyValueMapping, LegacyValueMap, and LegacyRangeMap types, and getMappedValue function from grafana-data. Migration is as follows:

Old New
LegacyBaseMap MappingType
LegacyValueMapping ValueMapping
LegacyValueMap ValueMap
LegacyRangeMap RangeMap
getMappedValue getValueMappingResult

This change fixes a bug in Grafana where intermittent failure of database, network between Grafana and the database, or error in querying the database would cause all alert rules to be unscheduled in Grafana. Following this change scheduled alert rules are not updated unless the query is successful.

The get_alert_rules_duration_seconds metric has been renamed to schedule_query_alert_rules_duration_seconds. Issue #49874

  • Any secret (data sources credential, alert manager credential, etc, etc) created or modified with Grafana v9.0 won't be decryptable from any previous version (by default) because the way encrypted secrets are stored into the database has changed. Although secrets created or modified with previous versions will still be decryptable by Grafana v9.0.

  • If required, although generally discouraged, the disableEnvelopeEncryption feature toggle can be enabled to keep envelope encryption disabled once updating to Grafana v9.0.

  • In case of need to rollback to an earlier version of Grafana (i.e. Grafana v8.x) for any reason, after being created or modified any secret with Grafana v9.0, the envelopeEncryption feature toggle will need to be enabled to keep backwards compatibility (only from v8.3.x a bit unstable, from 8.5.x stable).

  • As a final attempt to deal with issues related with the aforementioned situations, the grafana-cli admin secrets-migration rollback command has been designed to move back all the Grafana secrets encrypted with envelope encryption to legacy encryption. So, after running that command it should be safe to disable envelope encryption and/or roll back to a previous version of Grafana.

  • Alternatively or complementarily to all the points above, backing up the Grafana database before updating could be a good idea to prevent disasters (although the risk of getting some secrets corrupted only applies to those updates/created with after updating to Grafana v9.0). Issue #49301

  • According to the dynamic labels documentation, you can use up to five dynamic values per label. There’s currently no such restriction in the alias pattern system, so if more than 5 patterns are being used the GetMetricData API will return an error.

  • Dynamic labels only allow ${LABEL} to be used once per query. There’s no such restriction in the alias pattern system, so in case more than 1 is being used the GetMetricData API will return an error.

  • When no alias is provided by the user, Grafana will no longer fallback with custom rules for naming the legend.

  • In case a search expression is being used and no data is returned, Grafana will no longer expand dimension values, for instance when using a multi-valued template variable or star wildcard * in the dimension value field. Ref https://github.com/grafana/grafana/issues/20729

  • Time series might be displayed in a different order. Using for example the dynamic label ${PROP('MetricName')}, might have the consequence that the time series are returned in a different order compared to when the alias pattern {{metric}} is used

Issue #49173

In Elasticsearch, browser access mode was deprecated in grafana 7.4.0 and removed in 9.0.0. If you used this mode, please switch to server access mode on the datasource configuration page. Issue #49014

Environment variables passed from Grafana to external Azure plugins have been renamed:

  • AZURE_CLOUD renamed to GFAZPL_AZURE_CLOUD
  • AZURE_MANAGED_IDENTITY_ENABLED renamed to GFAZPL_MANAGED_IDENTITY_ENABLED
  • AZURE_MANAGED_IDENTITY_CLIENT_ID renamed to GFAZPL_MANAGED_IDENTITY_CLIENT_ID

There are no known plugins which were relying on these variables. Moving forward plugins should read Azure settings only via Grafana Azure SDK which properly handles old and new environment variables. Issue #48954

Removes support for for ElasticSearch versions after their end-of-life, currently versions < 7.10.0. To continue to use ElasticSearch data source, upgrade ElasticSearch to version 7.10.0+.
Issue #48715

Application Insights and Insight Analytics queries in Azure Monitor were deprecated in Grafana 8.0 and finally removed in 9.0. Deprecated queries will no longer be executed. Please refer to the documentation for more information about this change.

Issue #48328

grafana/ui: Button now specifies a default type="button"

The Button component provided by @grafana/ui now specifies a default type="button" when no type is provided. In previous versions, if the attribute was not specified for buttons associated with a <form> the default value was submit per the specification

You can preserve the old behavior by explicitly setting the type attribute: <Button type="submit" />

Github Issue #41863.
Issue #48183

The Rename by regex transformation has been improved to allow global patterns of the form /<stringToReplace>/g. Depending on the regex match used, this may cause some transformations to behave slightly differently. You can guarantee the same behaviour as before by wrapping the match string in forward slashes (/), e.g. (.*) would become /(.*)/ Issue #48179

<Select /> menus will now portal to the document body by default. This is to give more consistent behaviour when positioning and overlaying. If you were setting menuShouldPortal={true} before you can safely remove that prop and behaviour will be the same. If you weren't explicitly setting that prop, there should be no visible changes in behaviour but your tests may need updating. Please see the original PR (https://github.com/grafana/grafana/pull/36398) for migration guides. If you were setting menuShouldPortal={false} this will continue to prevent the menu from portalling.

Issue #48176

Grafana alerting endpoint prefixed with api/v1/rule/test that tests a rule against a Corte/Loki data source now expects the data source UID as a path parameter instead of the data source numeric identifier. Issue #48070

Grafana alerting endpoints prefixed with api/prometheus/ that proxy requests to a Cortex/Loki data source now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue #48052

Grafana alerting endpoints prefixed with api/ruler/ that proxy requests to a Cortex/Loki data source now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue #48046

Grafana alerting endpoints prefixed with api/alertmanager/ that proxy requests to an Alertmanager now expect the data source UID as a path parameter instead of the data source numeric identifier. Issue #47978

The format of log messages have been updated, lvl is now level and erorand dbug has been replaced with error and debug. The precision of timestamps has been increased. To smooth the transition, it is possible to opt-out of the new log format by enabling the feature toggle oldlog. This option will be removed in a future minor release. Issue #47584

In the Loki data source, the dataframe format used to represent Loki logs-data has been changed to a more efficient format. The query-result is represented by a single dataframe with a "labels" column, instead of the separate dataframes for every labels-value. When displaying such data in explore, or in a logs-panel in the dashboard will continue to work without changes, but if the data was loaded into a different dashboard-panel, or Transforms were used, adjustments may be necessary. For example, if you used the "labels to fields" transformation with the logs data, please switch to the "extract fields" transformation. Issue #47153

Deprecations

setExploreQueryField, setExploreMetricsQueryField and setExploreLogsQueryField are now deprecated and will be removed in a future release. If you need to set a different query editor for Explore, conditionally render based on props.app in your regular query editor. Please refer to https://grafana.com/docs/grafana/latest/developers/plugins/add-support-for-explore-queries/ for more informations.
Issue #48701

Plugin development fixes & changes

grafana - 8.5.5 (2022-06-06)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Azure Monitor: Include datasource ref when interpolating variables. #49543, @kevinwcyu
  • CloudWatch: Add multi-value template variable support for log group names in logs query builder. #49737, @kevinwcyu
  • Cloudwatch: Add template variable query function for listing log groups. #50100, @yaelleC

Bug fixes

grafana - 9.0.0-beta3 (2022-06-06)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Alerting: Add provenance guard to config api. #50147, @JohnnyQQQQ
  • Alerting: Make folder filter clearable in Alert list panel. #50093, @peterholmberg
  • Alerting: Provisioning API - Alert rules. #47930, @JohnnyQQQQ
  • Alerting: Remove Image Upload code from Slack notifier. #50062, @joeblubaugh
  • Alerting: Remove double quotes from matchers. #50038, @gotjosh
  • Cloudwatch: Dynamic labels autocomplete. #49794, @sunker
  • Datasource: Remove deprecated max_idle_connections_per_host setting. #49948, @marefr
  • Datasource: Remove support for unencrypted passwords. #49987, @marefr
  • Dependencies: Update to Golang version 1.17.11. #50253, @dsotirakis
  • Loki: Run query when pressing Enter on line-filters. #49913, @svennergr
  • Metrics: Remove support for using summaries instead of histogram for HTTP instrumentation. #49985, @bergquist
  • Plugins: Remove deprecated /api/tsdb/query metrics endpoint. #49916, @wbrowne
  • Plugins: Support headers field for check health. #49930, @marefr
  • Prometheus/Loki: Add raw query and syntax highlight in explain mode. #50070, @aocenas
  • Prometheus: Migrate metadata queries to use resource calls. #49921, @srclosson
  • RBAC: Make RBAC action names more consistent. #49730, @IevaVasiljeva
  • RBAC: Make RBAC action names more consistent. (Enterprise)
  • Settings: Sunset non-duration based login lifetime config. #49944, @sakjur
  • [9.0.x] Alerting: Update alert rule diff to not see difference between nil and empty map. #50198, @yuri-tceretian

Bug fixes

  • Alerting: Fix alert list panel showing firing alerts with no instances. #50069, @gillesdemey
  • Alerting: Fix notification policy "Override grouping" form save. #50031, @JacobsonMT
  • Alerting: Remove double quotes from matchers. #50046, @alexweav
  • Alerting: Use correct permission scope for external AM updates. #50159, @gillesdemey
  • Datasource: Fix allowed cookies to be forwarded as header to backend datasources. #49541, @marefr
  • Licensing: Fix trial expiration warning. (Enterprise)
  • Loki: Fix uncaught errors if labelKey contains special characters. #49887, @svennergr
  • Prometheus: Fix aligning of labels of exemplars after backend migration. #49924, @aocenas
  • SharePDF: Fix repeated datasource variables in PDF. (Enterprise)
  • State Timeline: Fix Null Value Filling and Value Transformation. #50054, @codeincarnate
  • Usage stats: Divide collection into multiple functions to isolate failures. #49928, @sakjur

Breaking changes

Removes support for storing/using datasource password and basicAuthPassword unencrypted which was deprecated in Grafana v8.1.0. Please use secureJsonData.password and secureJsonData.basicAuthPassword. Issue #49987

Removes the option to instrument HTTP request in Grafana using summaries instead of histograms. Issue #49985

Removes support for deprecated dataproxy.max_idle_connections_per_host setting. Please use max_idle_connections instead. Issue #49948

Removes the deprecated getFormStyles function from grafana-ui.
Prefer using GrafanaTheme2 and the useStyles2 hook. Issue #49945

The configuration options auth.login_maximum_inactive_lifetime_days and auth.login_maximum_lifetime_days were deprecated in Grafana v7.2.0 and have now been removed. Use login_maximum_inactive_lifetime_duration and login_maximum_lifetime_duration to customize the maximum lifetime of a login session. Issue #49944

Removed the deprecated isFocused and isInvalid props from the InlineLabel component. These props haven't done anything for a while, so migration is just a matter of removing the props. Issue #49929

Removed the deprecated onColorChange prop from ColorPicker. Moving forward the onChange prop should be used. Issue #49923

/api/tsdb/query API has been removed. Use /api/ds/query instead.
Issue #49916

onClipboardCopy and onClipboardError APIs have been changed such that the callback's argument is just the text that's been copied rather than the old ClipboardEvent interface.
Migration should just be a matter of going from

<ClipboardButton
  {/*other props... */}
  onClipboardCopy={(e) => {
    console.log(`Text "${e.text}" was copied!`);
  }}
/>

to

<ClipboardButton
  {/* other props... */}
  onClipboardCopy={(copiedText) => {
    console.log(`Text "${copiedText}" was copied!`);
  }}
/>

Related Issue #49847

The following RBAC action renames have been carried out:

  • users.authtoken:update -> users.authtoken:write;
  • users.password:update -> users.password:write;
  • users.permissions:update -> users.permissions:write;
  • users.quotas:update -> users.quotas:write;
  • org.users.role:update -> org.users:write;
  • alert.instances:update -> alert.instances:write;
  • alert.rules:update -> alert.rules:write;
  • users.authtoken:list -> users.authtoken:read;
  • users.quotas:list -> users.quotas:read;
  • users.teams:read -> replaced by users.read + teams:read

We've added a migration from the old action names to the new names and have updated our documentation. But you will have to update any scripts and provisioning files that are using the old action names. Issue #49730

The following RBAC action renames have been carried out:

  • reports.admin:write -> reports:write;
  • reports.admin:create -> reports:create;
  • licensing:update -> licensing:write;
  • roles:list -> roles:read;
  • teams.roles:list -> teams.roles:read;
  • users.roles:list -> users.roles:read;
  • users.permissions:list -> users.permissions:read

We've added a migration from the old action names to the new names and have updated our documentation. But you will have to update any scripts and provisioning files that are using the old action names. Issue #3372

Plugin development fixes & changes

grafana - 9.0.0-beta2 (2022-05-31)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

Bug fixes

Breaking changes

Drop support for deprecated setting ldap_sync_ttl under [auth.proxy]
Only sync_ttl will work from now on Issue #49902

Removes support for deprecated heading and description props. Moving forward, the Card.Heading and Card.Description components should be used. Issue #49885

Removes the deprecated link variant from the Button component.
To migrate, replace any usage of variant="link" with fill="text". Issue #49843

Removes the deprecated surface prop from the IconButton component. This prop hasn't actually done anything for a while, so it should be safe to just remove any instances of its usage.
Issue #49715

Removes the deprecated TextDisplayOptions export from @grafana/data in favor of VizTextDisplayOptions from @grafana/schema. To migrate, just replace usage of TextDisplayOptions with VizTextDisplayOptions. Issue #49705

Removed support for the deprecated getColorForTheme(color: string, theme: GrafanaTheme) function in favor of the
theme.visualization.getColorByName(color: string) method. The output of this method is identical to the removed function, so migration should just be a matter of rewriting calls of getColorForTheme(myColor, myTheme) to myTheme.visualization.getColorByName(myColor).
Issue #49519

In the Prometheus data source, for consistency and performance reasons, we changed how we represent NaN (not a number) values received from Prometheus. In the past versions, we converted these to null in the frontend (for dashboard and explore), and kept as NaN in the alerting path. Starting with this version, we will always keep it as NaN. This change should be mostly invisible for the users. Issue #49475

Plugins using custom Webpack configs could potentially break due to the changes between webpack@4 and webpack@5. Please refer to the official migration guide for assistance.

Webpack 5 does not include polyfills for node.js core modules by default (e.g. buffer, stream, os). This can result in failed builds for plugins. If polyfills are required it is recommended to create a custom webpack config in the root of the plugin repo and add the required fallbacks:

// webpack.config.js

module.exports.getWebpackConfig = (config, options) => ({
  ...config,
  resolve: {
    ...config.resolve,
    fallback: {
      os: require.resolve('os-browserify/browser'),
      stream: require.resolve('stream-browserify'),
      timers: require.resolve('timers-browserify'),
    },
  },
});

Please refer to the webpack build error messages or the official migration guide for assistance with fallbacks.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

It does not bump the following dependencies to the very latest due to the latest versions being ES modules:

  • ora
  • globby
  • execa
  • chalk
    Issue #47826

We have changed the internals of backendSrv.fetch() to throw an error when the response is an incorrect JSON.

// PREVIOUSLY: this was returning with an empty object {} - in case the response is an invalid JSON
return await getBackendSrv().post(`${API_ROOT}/${id}/install`);

// AFTER THIS CHANGE: the following will throw an error - in case the response is an invalid JSON
return await getBackendSrv().post(`${API_ROOT}/${id}/install`);

When is the response handled as JSON?

  • If the response has the "Content-Type: application/json" header, OR
  • If the backendSrv options (BackendSrvRequest) specify the response as JSON: { responseType: 'json' }

How does it work after this change?

  • In case it is recognised as a JSON response and the response is empty, it returns an empty object {}
  • In case it is recognised as a JSON response and it has formatting errors, it throws an error

How to migrate?
Make sure to handle possible errors on the callsite where using backendSrv.fetch() (or any other backendSrv methods). Issue #47493

Plugin development fixes & changes

grafana - 8.5.4 (2022-05-30)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Alerting: Remove disabled flag for data source when migrating alerts. #48559, @yuri-tceretian
  • Alerting: Show notification tab of legacy alerting only to editor. #49624, @yuri-tceretian
  • Alerting: Update migration to migrate only alerts that belong to existing org\dashboard. #49192, @yuri-tceretian
  • AzureMonitor: Do not quote variables when a custom "All" variable option is used. #49428, @andresmgot
  • AzureMonitor: Update allowed namespaces. #48468, @jcolladokuri
  • CloudMonitor: Correctly encode default project response. #49510, @aangelisc
  • Cloudwatch: Add support for new AWS/RDS EBS* metrics. #48798, @szymonpk
  • InfluxDB: Use backend for influxDB by default via feature toggle. #48453, @yesoreyeram
  • Legend: Use correct unit for percent and count calculations. #49004, @dprokop
  • LokI: use millisecond steps in Grafana 8.5.x. #48630, @gabor
  • Plugins: Introduce HTTP 207 Multi Status response to api/ds/query. #48550, @wbrowne
  • Reporting: Improve PDF file size using grid layout. (Enterprise)
  • Transformations: Add an All Unique Values Reducer. #48653, @josiahg
  • Transformers: avoid error when the ExtractFields source field is missing. #49368, @wardbekker
  • [v8.5.x] Alerting: Update migration to migrate only alerts that belong to existing org\dashboard. #49199, @grafanabot
  • [v8.5.x] Reporting: Improve PDF file size using grid layout. (Enterprise)

Bug fixes

  • Alerting: Allow disabling override timings for notification policies. #48648, @gillesdemey
  • Alerting: Allow serving images from custom url path. #49022, @gillesdemey
  • Alerting: Apply Custom Headers to datasource queries. #47860, @joeblubaugh
  • Alerting: Fix RBAC actions for notification policies. #49185, @yuri-tceretian
  • Alerting: Fix access to alerts for viewer with editor permissions when RBAC is disabled. #49270, @yuri-tceretian
  • Alerting: Fix anonymous access to alerting. #49203, @yuri-tceretian
  • Alerting: correctly show all alerts in a folder. #48684, @gillesdemey
  • AzureMonitor: Fixes metric definition for Azure Storage queue/file/blob/table resources. #49101, @aangelisc
  • Dashboard: Fix dashboard update permission check. #48746, @IevaVasiljeva
  • DashboardExport: Fix exporting and importing dashboards where query data source ended up as incorrect. #48410, @torkelo
  • FileUpload: clicking the Upload file button now opens the modal correctly. #48766, @ashharrison90
  • GrafanaUI: Fix color of links in error Tooltips in light theme. #49327, @joshhunt
  • LibraryPanels: Fix library panels not connecting properly in imported dashboards. #49161, @joshhunt
  • Loki: Improve unpack parser handling. #49074, @gabor
  • RolePicker: Fix menu position on smaller screens. #48429, @Clarity-89
  • TimeRange: Fixes updating time range from url and browser history. #48657, @torkelo
  • TimeSeries: Fix detection & rendering of sparse datapoints. #48841, @leeoniya
  • Timeseries: Fix outside range stale state. #49633, @ryantxu
  • Tooltip: Fix links not legible in Tooltips when using light theme. #48748, @joshhunt
  • Tooltip: Sort decimals using standard numeric compare. #49084, @dprokop
  • Transforms: Labels to fields, fix label picker layout. #49304, @torkelo
  • Variables: Fixes issue with data source variables not updating queries with variable. #49478, @torkelo
  • [v8.5.x] Alerting: Fix RBAC actions for notification policies (#49185). #49348, @yuri-tceretian
  • [v8.5.x] Alerting: Fix access to alerts for viewer with editor permissions when RBAC is disabled. #49427, @konrad147
  • [v8.5.x] Alerting: Fix anonymous access to alerting. #49268, @yuri-tceretian

Breaking changes

For a data source query made via /api/ds/query :

  • If the DatasourceQueryMultiStatus feature is enabled and
    • The data source response has an error set as part of the DataResponse, the resulting HTTP status code is now 207 Multi Status instead of 400 Bad gateway
  • If the DatasourceQueryMultiStatus feature is not enabled and
    • The data source response has an error set as part of the DataResponse, the resulting HTTP status code is 400 Bad Request (no breaking change)
      --> Issue #48550
grafana - 9.0.0-beta1 (2022-05-24)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • AccessControl: Add setting for permission cache. (Enterprise)
  • AccessControl: Check dashboard permissions for reports. (Enterprise)
  • Auth: Remove grafana ui dependency to the aws sdk. #43559, @sunker
  • BasicRoles: Add API endpoint to reset basic roles permissions to factory. (Enterprise)
  • LDAP Mapping: Allow Grafana Admin mapping without org role. #37189, @krzysdabro
  • Licensing: Only enforce total number of users. (Enterprise)
  • Loki: do not convert NaN to null. #45389, @gabor
  • Report: API support for multiple dashboards. (Enterprise)
  • Report: Support sending embedded image in the report email. (Enterprise)
  • Report: UI for multiple dashboards. (Enterprise)
  • Reporting: Remove redundant empty attachment when export to CSV is enabled. (Enterprise)
  • SAML: Implement Name Templates for assertion_attribute_name option. (Enterprise)
  • SSE/Alerting: Support prom instant vector responses. #44865, @kylebrandt
  • Tracing: Add trace to metrics config behind feature toggle. #46298, @connorlindsey

Bug fixes

  • Fix: Prevent automatic parsing of string data types to numbers. #46035, @joshhunt
  • Prometheus: Fix inconsistent labels in exemplars resulting in marshal json error. #46135, @hanjm

Breaking changes

In the Loki data source, for consistency and performance reasons, we changed how we represent NaN (not a number) values received from Loki. In the past versions, we converted these to null in the frontend (for dashboard and explore), and kept as NaN in the alerting path. Starting with this version, we will always keep it as NaN. This change should be mostly invisible for the users. Issue #45389

The dependency to grafana/aws-sdk is moved from grafana/ui to the plugin. This means that any plugin that use SIGV4 auth need to pass a SIGV4 editor component as a prop to the DataSourceHttpSettings component. Issue #43559

grafana - 8.5.3 (2022-05-19)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Bug fixes

grafana - 7.5.16 (2022-05-19)

Published by xlson over 2 years ago

Download page
What's new highlights

Bug fixes

  • Security: Fixes CVE-2022-29170
grafana - 8.5.2 (2022-05-03)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Alerting: Add safeguard for migrations that might cause dataloss. #48526, @JohnnyQQQQ
  • AzureMonitor: Add support for not equals and startsWith operators when creating Azure Metrics dimension filters. #48077, @aangelisc
  • Elasticsearch: Add deprecation notice for < 7.10 versions. #48506, @ivanahuckova
  • Traces: Filter by service/span name and operation in Tempo and Jaeger. #48209, @joey-grafana

Bug fixes

  • AzureAd Oauth: Fix strictMode to reject users without an assigned role. #48474, @kyschouv
  • CloudWatch: Fix variable query tag migration. #48587, @iwysiu
  • Plugins: Ensure catching all appropriate 4xx api/ds/query scenarios. #47565, @wbrowne
grafana - 8.5.1 (2022-04-27)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Bug fixes

grafana - 8.5.0 (2022-04-21)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Alerting: Add contact points provisioning API. #47197, @JohnnyQQQQ
  • Alerting: Add resolved count to notification title when both firing and resolved present. #46697, @JacobsonMT
  • Alerting: Alert rule should wait For duration when execution error state is Alerting. #47052, @grobinson-grafana
  • Alerting: Classic conditions can now display multiple values. #46971, @gotjosh
  • Alerting: Display query from grafana-managed alert rules on /api/v1/rules. #45969, @gotjosh
  • Alerting: Enhance support for arbitrary group names in managed alerts. #47785, @gillesdemey
  • Alerting: add field for custom slack endpoint. #45751, @nathanrodman
  • Azure Monitor : Adding json formatting of error messages in Panel Header Corner and Inspect Error Tab. #44877, @yaelleC
  • Azure Monitor: Add 2 more Curated Dashboards for VM Insights. #45187, @jcolladokuri
  • CloudWatch: Handle new error codes for MetricInsights. #47033, @Gabrielopesantos
  • Dashboards: show changes in save dialog. #46557, @ryantxu
  • DataSource: Default data source is no longer a persisted state but just the default data source for new panels. #45132, @torkelo
  • DataSourcePlugin API: Allow queries import when changing data source type. #47435, @dprokop
  • Explore: Remove return to panel button. #45018, @gelicia
  • Explore: allow users to save Explore state to a new panel in a new dashboard. #45148, @Elfo404
  • Instrumentation: Proxy status code correction and various improvements. #47473, @marefr
  • Logging: Introduce feature toggle to activate gokit/log format. #47336, @ying-jeanne
  • NewsPanel: Add support for Atom feeds. #45390, @kaydelaney
  • Plugins: Add deprecation notice for /api/tsdb/query endpoint. #45238, @wbrowne
  • Plugins: Adding support for traceID field to accept variables. #45559, @vinisdl
  • PostgreSQL: __unixEpochGroup to support arithmetic expression as argument. #46764, @s0nik42
  • Profile/Help: Expose option to disable profile section and help menu. #46308, @cameronwaterman
  • Prometheus: Enable new visual query builder by default. #46634, @torkelo
  • SAML: Allow disabling of SAML signups. #47481, @mmandrus
  • SAML: Allow disabling of SAML signups. (Enterprise)
  • Table: New pagination option. #45732, @zoltanbedi
  • TablePanel: Add cell inspect option. #45620, @dprokop
  • Tempo / Trace Viewer: Support Span Links in Trace Viewer. #45632, @Shachi16
  • Tempo: Download span references in data inspector. #47074, @connorlindsey
  • Tempo: Separate trace to logs and loki search datasource config. #46655, @connorlindsey
  • Trace View: Show number of child spans. #44393, @tharun208
  • Transformations: Support escaped characters in key-value pair parsing. #47901, @aangelisc

Bug fixes

  • Azure Monitor: Bug Fix for incorrect variable cascading for template variables. #47478, @jcolladokuri
  • CloudWatch: List all metrics properly in SQL autocomplete. #45898, @sunker
  • CloudWatch: Run query on blur in logs query field. #47454, @fridgepoet
  • Dashboard: Template variables are now correctly persisted when clicking breadcrumb links. #46790, @ashharrison90
  • DashboardPage: Remember scroll position when coming back panel edit / view panel. #47639, @torkelo
  • Panel Edit: Options search now works correctly when a logarithmic scale option is set. #47927, @ashharrison90
  • Postgres: Return tables with hyphenated schemes. #45754, @zuchka
  • Table panel: Fix horizontal scrolling when pagination is enabled. #47776, @dprokop
  • Variables: Ensure variables in query params are correctly recognised. #47049, @ashharrison90
  • Variables: Fix crash when changing query variable datasource. #44957, @joshhunt
  • Visualizations: Stack negative-valued series downwards. #47373, @leeoniya

Breaking changes

For a proxied request, e.g. Grafana's datasource or plugin proxy:

  • If the request is cancelled, e.g. from the browser/by the client, the HTTP status code is now 499 Client closed request instead of 502 Bad gateway
  • If the request times out, e.g. takes longer time than allowed, the HTTP status code is now 504 Gateway timeout instead of 502 Bad gateway. Issue #47473

The change in behavior is that negative-valued series are now stacked downwards from 0 (in their own stacks), rather than downwards from the top of the positive stacks. We now automatically group stacks by Draw style, Line interpolation, and Bar alignment, making it impossible to stack bars on top of lines, or smooth lines on top of stepped lines. Issue #47373

The meaning of the default data source has now changed from being a persisted property in a panel. Before when you selected the default data source for a panel and later changed the default data source to another data source it would change all panels who were configured to use the default data source. From now on the default data source is just the default for new panels and changing the default will not impact any currently saved dashboards. Issue #45132

The Tooltip component provided by @grafana/ui is no longer automatically interactive (that is you can hover onto it and click a link or select text). It will from now on by default close automatically when you mouse out from the trigger element. To make tooltips behave like before set the new interactive property to true.
Issue #45053

Deprecations

/api/tsdb/query API has been deprecated and will be removed in a future release. Use /api/ds/query instead. Issue #45238

Plugin development fixes & changes

grafana - 8.4.7 (2022-04-19)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

Bug fixes

  • API: Include userId, orgId, uname in request logging middleware. #47183, @marefr
  • Elasticsearch: Respect maxConcurrentShardRequests datasource setting. #47120, @alexandrst88
grafana - 8.4.6 (2022-04-12)

Published by grafanabot over 2 years ago

Download page
What's new highlights

  • Security: Fixes CVE-2022-24812. For more information, see our blog
grafana - 8.5.0-beta1 (2022-04-06)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Add config option to enable/disable reporting. (Enterprise)
  • Alerting: Accurately set value for prom-compatible APIs. #47216, @gotjosh
  • Alerting: Provisioning API - Notification Policies. #46755, @alexweav
  • Analytics: Enable grafana and plugin update checks to be operated independently. #46352, @wbrowne
  • Azure Monitor: Add support for multiple template variables in resource picker. #46215, @sarahzinger
  • Caching: Add separate TTL for resources cache. (Enterprise)
  • Caching: add support for TLS configuration for Redis Cluster. (Enterprise)
  • NewsPanel: Remove Use Proxy option and update documentation with recommendations. #47189, @joshhunt
  • OAuth: Sync GitHub OAuth user name to Grafana if it's set. #45438, @pallxk

Bug fixes

  • Plugins: Fix Default Nav URL for dashboard includes. #47143, @wbrowne

Breaking changes

When user is using Github OAuth, GitHub login is showed as both Grafana login and name. Now the GitHub name is showed as Grafana name, and GitHub login is showed as Grafana Login. Issue #45438

The meaning of the default data source has now changed from being a persisted property in a panel. Before when you selected the default data source for a panel and later changed the default data source to another data source it would change all panels who were configured to use the default data source. From now on the default data source is just the default for new panels and changing the default will not impact any currently saved dashboards. Issue #45132

grafana - 8.4.5 (2022-03-31)

Published by grafanabot over 2 years ago

Download page
What's new highlights

Features and enhancements

  • Instrumentation: Make backend plugin metrics endpoints available with optional authentication. #46467, @marefr
  • Table panel: Show datalinks for cell display modes JSON View and Gauge derivates. #46020, @mdvictor

Bug fixes

  • Azure Monitor: Small bug fixes for Resource Picker. #46665, @sarahzinger
  • Logger: Use specified format for file logger. #46970, @sakjur
  • Logs: Handle missing fields in dataframes better. #46963, @gabor
  • ManageDashboards: Fix error when deleting all dashboards from folder view. #46877, @joshhunt
Package Rankings
Top 0.57% on Npmjs.org
Top 0.35% on Proxy.golang.org
Badges
Extracted from project README
License Drone Go Report Card