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)
Published by grafanabot almost 3 years ago
Download page
What's new highlights
OK
if at least one, but not all, conditions returned no data. This change fixes that bug such that in Grafana 8.2.5 these alert rules now evaluate to No Data
. If an alert should evaluate to OK
when one or all conditions return No Data
then this can be done via changing If no data or all values are null
to OK
. However, this will not preserve the old behaviour in 8.2.4 where an alert will be OK
if at least one, but not all, conditions return no data and then No Data
if all conditions return No Data
.Published by grafanabot almost 3 years ago
Published by grafanabot almost 3 years ago
Published by grafanabot almost 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
ngalert
feature toggle and introduce two new settings for enabling Grafana 8 alerts and disabling them for specific organisations. #38746, @papagian
Grafana v8.2.0-beta1 caused data loss for users having enabled ngalert
in 8.0.x - 8.1.x and created alerts using the new alerting system. This issue is now fixed except if the deployment has multiple organizations and the feature flag was enabled in the previous version (8.0.x - 8.1.x).
In this scenario (upgrade from 8.0.x - 8.1.x with multiple organizations and ngalert
enabled to 8.2.0-beta2), the migration will assign existing notification policies and contact points to the first organization and then apply the default alertmanager configuration to all organizations. This will effectively reset notification policies for all organizations. Issue #39541
ngalert
feature toggle it has been deprecated it will be removed in a future release. To enable Grafana 8 alerts, modify your configuration and:
unified_alerting
section set the enabled
property to true
alerting
section set the enabled
property to false
Issue #38746
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
response_limit
for datasource responses. #38962, @dsotirakis
trace to logs
feature. #38943, @connorlindsey
/var/run
to /run
. #35739, @MichaIng
The monaco-editor
dependency in grafana-ui
has been updated to a newer version (0.27.0
), which is not completely backward compatible with the old version (0.21.2
). The backward incompatible changes are fairly small, but they do exist, so if your code accesses the raw monaco-objects through the grafana-ui
package, please check the monaco-editor changelog and apply any necessary changes. Issue #39027
The mandatory css
prop in grafana/ui
components has been removed.
Previous versions of grafana/ui
components were typed incorrectly due to a dependency mismatch between emotion 10 and 11 causing a css
prop to be added to components that extended react types.
Issue #38078
Panel queries and/or annotation queries that used more than one statistic will be converted into one query/annotation per statistic. In case an alerting rule was based on a query row that had more than one statistic, it would now be based only on the first statistic for that query row. New alerting rules will not be created for migrated queries. Please note that in most cases it would not make sense to have an alerting rule that is based on multiple statistics anyway. Issue #36925
getHighlighterExpressions
in datasource APIs ( used to highlight logs while editing queries) has been deprecated and will be removed in a future release.
ExploreQueryFieldProps
interface for query editors has been deprecated and will be removed in a future release. Use QueryEditorProps
instead. Issue #38942
Published by grafanabot about 3 years ago
Download page
What's new highlights
/
as separator. #39185, @dsotirakis
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
false
into true
. #37402, @simPod
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
go mod verify
until all required files are copied over. #37246, @wbrowne
Published by grafanabot about 3 years ago
Download page
What's new highlights
Published by grafanabot about 3 years ago
Download page
What's new highlights
dataproxy_max_idle_connections
config variable. #35864, @dsotirakis
When parsing Elasticsearch query responses using template variables, each field gets named after the variable value instead of the name.
For example, executing a terms
aggregation on a variable named $groupBy
that has @hostname
as a value, the resulting column in the table response will be @hostname
instead of $groupBy
Issue #36035
Azure Monitor data source no longer supports different credentials for Metrics and Logs in existing data sources. To use different credentials for Azure Monitor Logs, create another data source. Issue #35121
Existing Azure Metrics Logs queries for Log Analytics Workspaces should be backward compatible with this change and should not get impacted. Panels will be migrated to use the new resource-centric backend when you first edit and save them.
Application Insights and Insights Analytics queries are now read-only and cannot be modified. To update Application Insights queries, users can manually recreate them as Metrics queries, and Insights Analytics are recreated with Logs.
Issue #33879