1+++ 2title = "What's new in Grafana v7.5" 3description = "Feature and improvement highlights for Grafana v7.5" 4keywords = ["grafana", "new", "documentation", "7.5", "release notes"] 5weight = -32 6aliases = ["/docs/grafana/latest/guides/whats-new-in-v7-5/"] 7[_build] 8list = false 9+++ 10 11# What’s new in Grafana v7.5 12 13This topic includes the release notes for Grafana v7.5. For all details, read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md). 14 15## Grafana OSS features 16 17These features are included in the Grafana open source edition. 18 19### Pie chart panel visualization (beta) 20 21Grafana 7.5 adds a beta version of the next-generation pie chart panel. 22 23 24 25For more information, refer to [Pie chart panel]({{< relref "../visualizations/pie-chart-panel.md" >}}). 26 27### Alerting for Loki 28 29Grafana 7.5 comes with alerting support for Loki. With LogQL you can wrap a log query with the functions that allow for creating metrics out of the logs, such as "rate()". Metric queries can then be used to calculate things such as the rate of error messages. [When combined with log parsers](https://www.youtube.com/watch?v=H9z2V0Ib1q0), they can be used to calculate metrics from a value within the log line, such latency or request size. 30 31With alerting support for Loki, you can now create alerts on Loki metrics queries. 32 33[Alerting]({{< relref "../alerting/_index.md" >}}) was updated as a result of this change. 34 35 36 37### Loki label browser 38 39A new Loki logs browser lets you construct the queries step by step: you choose labels that you like to consider, such as "job", then you select the values that you like, such as "my-app1". Note that you can select values from more than one label, and that they get facetted. This means only possible label combinations are selectable. When you're done, you can run the query either as a logs or a metrics query (a metrics query returns the log volume in a chart). 40 41### Changed default HTTP method for new Prometheus data sources 42 43For new Prometheus data sources, we have changed the default HTTP method to POST. POST allows for much larger query bodies than using the GET method. This is necessary when sending queries from graphs with a lot of targets, for example, many hosts in a dashboard variable. The POST method also makes the Query Inspector data easier to read since the query is in plain text whereas the GET query is URL encoded. 44 45> **Note:** This is not going to affect provisioned data sources or already created data sources. 46 47[Prometheus data source]({{< relref "../datasources/prometheus.md" >}}) was updated as a result of this change. 48 49### Word highlighting for Elasticsearch 50 51When searching for text in Elasticsearch logs, matching words in the log line returned by the query are now highlighted. 52 53 54 55### Better format definition for trace data 56 57In Grafana 7.5, we changed how data for the trace view is sent from the data source. The required data frame has a clear format, which is more aligned with how data is generally represented in Grafana. This makes it easier for third-party developers to implement data sources leveraging the trace view. 58 59For more information, refer to [trace data API docs]({{< relref "../explore/trace-integration.md#data-api" >}}). 60 61### Paste in SSL certs for Postgres data source 62 63Previously, when users wanted to configure the Postgres data source to connect with SSL certification, they needed to put the certification on the server, and configure the data source with file path. 64 65Instead of the file path, users can now paste the SSL certification content in the UI. This allows them to configure the certification even when they do not have access to the server. 66 67> **Note:** It remains as limitation for the Grafana Cloud, as users may not have access to the server configuration. 68 69[Postgres data source]({{< relref "../datasources/postgres.md" >}}) and [Provisioning]({{< relref "../administration/provisioning.md" >}}) were updated as a result of this change. 70 71### Deprecation notice for some Azure Monitor queries 72 73In the upcoming Grafana 8.0 release, Application Insights and Insights Analytics query types within the Azure Monitor data source will be deprecated and be made read-only in favor of querying Application Insights from Metrics and Logs. 74 75Grafana 7.5 includes a deprecation notice for these queries, and some documentation to help users prepare for the upcoming changes. 76 77For more information, refer to [Deprecating Application Insights and Insights Analytics]({{< relref "../datasources/azuremonitor/_index.md#deprecating-application-insights-and-insights-analytics" >}}). 78 79### Cloudwatch data source enhancements 80 81- Support for region eu-south-1 has been added to the CloudWatch data source. New metrics have also been added to the namespaces AWS/Timestream, AWS/RDS (RDS Proxy metrics), AWS/NetworkFirewall, AWS/GroundStation, and AWS/DDoSProtection. Many thanks to [relvira](https://github.com/relvira), [ilyastoli](https://github.com/ilyastoli), and [rubycut](https://github.com/rubycut) for contributing! 82- Added a page limit to the List Metrics API call to improve speed and reduce memory consumption. You can change this limit by entering a higher value in [list_metrics_page_limit]({{< relref "../administration/configuration.md#list-metrics-page-limit" >}}) in the Grafana configuration file. 83- You can now enable or disable authentication providers and assume a role other than default by changing the [allowed_auth_providers]({{< relref "../administration/configuration.md#allowed-auth-providers" >}}) and [assume_role_enabled]({{< relref "../administration/configuration.md#assume-role-enabled" >}}) options in the Grafana configuration file. By default, the allowed authentication providers are _AWS SDK Default_, _Access and secret key_, and _Credentials File_, and role is _Assume role (ARN)_. 84- You can now specify a custom endpoint in the CloudWatch data source configuration page. This field is optional, and if it is left empty, then the default endpoint for CloudWatch is used. By specifying a regional endpoint, you can reduce request latency. 85 86 [AWS Cloudwatch data source]({{< relref "../datasources/aws-cloudwatch/_index.md" >}}) was updated as a result of this change. 87 88### Increased API limit for CloudMonitoring Services 89 90In previous versions, when querying metrics for Service Level Objectives (SLOs) in the CloudMonitoring data source, only the first 100 services were listed in the **Service** field list. To overcome this issue, the API limit for listing services has been increased to 1000. 91 92### Tempo as a backend data source 93 94We have converted Tempo to a backend data source and dropped support for tempo-query's (Jaeger) response. To configure it, you can now point to the port that is set in the Tempo configuration file. 95 96```yaml 97server: 98 http_listen_port: 3101 99``` 100 101[Azure Monitor data source]({{< relref "../datasources/azuremonitor/_index.md" >}}) was updated as a result of this change. 102 103## Enterprise features 104 105These features are included in the Grafana Enterprise edition. 106 107### Query caching 108 109When caching is enabled, Grafana temporarily stores the results of data source queries. When you or another user submit the same query again, the results return from the cache instead of from the data source (such as Splunk or ServiceNow). 110 111Query caching advantages: 112 113- Faster dashboard load times, especially for popular dashboards. 114- Reduced API costs. 115- Reduced likelihood that APIs will rate-limit or throttle requests. 116 117Caching currently works for all backend data sources. You can enable the cache globally or per data source, and you can configure the cache duration per data source. The cache is currently in-memory. 118 119For more information, refer to [Query caching]({{< relref "../enterprise/query-caching.md" >}}). 120 121### Use template variable in reports 122 123If you have created dashboards with template variables, then you can choose which values are selected when rendering a report. This makes it easier to tailor reports to their audience or generate multiple reports from the same dashboard. 124 125Enable this feature in configuration settings using the `templateVariables` flag. 126 127For more information, refer to [Reporting]({{< relref "../enterprise/reporting.md#choose-template-variables" >}}). 128 129### Active user limits 130 131If a Grafana instance has exceeded its licensed number of active users, then non-active users who try to sign in to Grafana will be prevented from doing so. Active users are users who have logged in to Grafana in the past 30 days. The total number of users registered in Grafana does not affect this rule. This enforcement is applied separately for Viewers and for Editor/Admins, so if you reach your active Viewer limit, new Editor/Admins will still be able to sign in. This rule also includes a 10% buffer, meaning that you need to exceed your limit by 10% before users are prevented from signing in. 132 133Here is an example: 134 135A Grafana Enterprise instance includes 100 Viewers and 50 Editor/Admins. Over the course of the last 30 days, 110 Viewers and 20 Editor/Admins have signed in to Grafana. 136 137All of the Viewers who have signed in over the past 30 days will retain the ability to sign in. 138 139When a previously-inactive Viewer (someone who has not signed in over the past 30 days) tries to sign in, they will see a message and be prevented from signing in until the number of active users dips back below 110. New Editor/Admins are not affected by this; they can continue to sign in until the number of active Editors/Admins reaches 55. 140 141If you try to sign in to a fourth device or browser, then you will be prevented from doing so; the limit of concurrent sessions is three. 142 143If you sign in to a fourth device or browser, then you will be signed out of the session that is least current. 144Concurrent session limits 145Each Grafana Enterprise user will be limited to three concurrent user sessions. When a user opens a fourth session, then the longest-inactive session will be automatically signed out. 146 147A new session is created when you sign in to Grafana from a different device or a different browser. Multiple windows and tabs in the same browser are all part of the same session, so having many Grafana tabs open will not cause any issues. 148 149For more information on Grafana Enterprise licensing and restrictions, refer to [License restrictions]({{< relref "../enterprise/license/license-restrictions.md" >}}). 150 151## Breaking changes 152 153There are no known breaking changes in this release. 154 155## Updated configuration 156 157``` 158[server] 159read_timeout = 0 160``` 161 162Sets the maximum time using a duration format (5s/5m/5ms) before timing out read of an incoming request and closing idle connections. 163`0` means there is no timeout for reading the request. 164
