IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-11-22 08:56:43 -06:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Update whats new 7 5 (#31875)

Browse Source 
* Update whats-new-in-v7-5.md

* Update whats-new-in-v7-5.md
This commit is contained in:
Diana Payton 2021-03-10 14:01:01 -08:00 committed by GitHub
parent 12a6e68763
commit 477a54ae54
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/sources/whatsnew/whats-new-in-v7-5.md
View File

@ -83,6 +83,15 @@ For more information, refer to [Deprecating Application Insights and Insights An
In 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.
### Tempo as a backend data source
We 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.
```yaml
server:
http_listen_port: 3101
```
## Enterprise features
These features are included in the Grafana Enterprise edition.
@ -98,12 +107,16 @@ Query caching advantages:
Caching 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.
For more information, refer to [Query caching]({{< relref "../enterprise/query-caching.md" >}}).
### Use template variable in reports
If 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.
Enable this feature in configuration settings using the `templateVariables` flag.
For more information, refer to [Reporting]({{< relref "../enterprise/reporting.md#choose-template-variables" >}}).
### Active user limits
If 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.
@ -126,15 +139,6 @@ A new session is created when you sign in to Grafana from a different device or
For more information on Grafana Enterprise licensing and restrictions, refer to [License restrictions]({{< relref "../enterprise/license-restrictions.md" >}}).
### Tempo as a backend data source
We have converted Tempo to a backend data source and dropped support for tempo-query's (Jaeger) response. To configure, you can now point to the port that is set in Tempo's configuration file.
```yaml
server:
http_listen_port: 3101
```
## Breaking changes
There are no known breaking changes in this release.