Docs: Grafana whats new 7.4 (#30404)

* Create whats-new-in-v7-4.md

* Update whats-new-in-v7-4.md

* Update types-options.md

* Update whats-new-in-v7-4.md

* Updated image paths

* minor edits

* updates

* content updates

* Update docs/sources/whatsnew/whats-new-in-v7-4.md

Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>

* Update docs/sources/whatsnew/whats-new-in-v7-4.md

Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>

Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com>

docs/sources/datasources/jaeger.md

@@ -33,7 +33,7 @@ This is a configuration for the [trace to logs feature]({{< relref "../explore/i
 - **Data source -** Target data source.
 - **Tags -** The tags that will be used in the Loki query. Default is `'cluster', 'hostname', 'namespace', 'pod'`.
 
-{{< docs-imagebox img="/img/docs/v74/trace-to-logs-settings.png" class="docs-image--no-shadow" caption="Screenshot of the trace to logs settings" >}}
+![Trace to logs settings](/img/docs/explore/trace-to-logs-settings-7-4.png "Screenshot of the trace to logs settings")
 
 ## Query traces
 

docs/sources/datasources/tempo.md

@@ -32,7 +32,7 @@ This is a configuration for the [trace to logs feature]({{< relref "../explore/i
 - **Data source -** Target data source.
 - **Tags -** The tags that will be used in the Loki query. Default is `'cluster', 'hostname', 'namespace', 'pod'`.
 
-{{< docs-imagebox img="/img/docs/v74/trace-to-logs-settings.png" class="docs-image--no-shadow" caption="Screenshot of the trace to logs settings" >}}
+![Trace to logs settings](/img/docs/explore/trace-to-logs-settings-7-4.png "Screenshot of the trace to logs settings")
 
 ## Query traces
 

docs/sources/datasources/zipkin.md

@@ -33,7 +33,7 @@ This is a configuration for the [trace to logs feature]({{< relref "../explore/i
 - **Data source -** Target data source.
 - **Tags -** The tags that will be used in the Loki query. Default is `'cluster', 'hostname', 'namespace', 'pod'`.
 
-{{< docs-imagebox img="/img/docs/v74/trace-to-logs-settings.png" class="docs-image--no-shadow" caption="Screenshot of the trace to logs settings" >}}
+![Trace to logs settings](/img/docs/explore/trace-to-logs-settings-7-4.png "Screenshot of the trace to logs settings")
 
 ## Query traces
 

docs/sources/explore/index.md

@@ -306,9 +306,9 @@ Clicking anywhere on the span row shows span details.
 
 > This feature is only available in Grafana 7.4+.
 
-You can navigate from a span in a trace view directly to logs relevant for that span. This is available for Tempo, Jaeger and Zipkin data source at this moment. See their relevant documentation for instruction how to configure this feature.
+You can navigate from a span in a trace view directly to logs relevant for that span. This is available for Tempo, Jaeger, and Zipkin data source at this moment. See their relevant documentation for instruction how to configure this feature.
 
-{{< docs-imagebox img="/img/docs/v74/trace-to-logs.png" class="docs-image--no-shadow" caption="Screenshot of the trace view in Explore with new icon next to the spans" >}}
+![Trace to logs](/img/docs/explore/trace-to-log-7-4.png "Screenshot of the trace to logs")
 
 Click the document icon to open a split view in Explore with the configured data source and query relevant logs for the span.
 

docs/sources/panels/transformations/types-options.md

@@ -7,20 +7,23 @@ weight = 300
 
 Grafana comes with the following transformations:
 
-- [Reduce](#reduce)
-- [Filter data by name](#filter-data-by-name)
-- [Filter data by query](#filter-data-by-query)
-- [Filter data by value](#filter-data-by-value)
-- [Organize fields](#organize-fields)
-- [Outer join](#join-by-field-outer-join)
-- [Series to rows](#series-to-rows)
-- [Add field from calculation](#add-field-from-calculation)
-- [Labels to fields](#labels-to-fields)
-- [Concatenate fields](#concatenate-fields)
-- [Sort by](#sort-by)
-- [Group by](#group-by)
-- [Merge](#merge)
-- [Rename by regex](#rename-by-regex)
+- [Transformation types and options](#transformation-types-and-options)
+  - [Reduce](#reduce)
+  - [Merge](#merge)
+  - [Filter data by name](#filter-data-by-name)
+  - [Filter data by query](#filter-data-by-query)
+  - [Organize fields](#organize-fields)
+  - [Join by field (outer join)](#join-by-field-outer-join)
+  - [Add field from calculation](#add-field-from-calculation)
+  - [Labels to fields](#labels-to-fields)
+    - [Value field name](#value-field-name)
+    - [Merging behavior](#merging-behavior)
+  - [Sort by](#sort-by)
+  - [Group by](#group-by)
+  - [Concatenate fields](#concatenate-fields)
+  - [Series to rows](#series-to-rows)
+  - [Filter data by value](#filter-data-by-value)
+  - [Rename by regex](#rename-by-regex)
 
 Keep reading for detailed descriptions of each type of transformation and the options available for each, as well as suggestions on how to use them.
 
@@ -373,20 +376,23 @@ Here is the result after applying the Series to rows transformation.
 
 This transformation allows you to filter your data directly in Grafana and remove some data points from your query result. You have the option to include or exclude data that match one or more conditions you define. The conditions are applied on a selected field.
 
-The available conditions are:
+This transformation is very useful if your data source does not natively filter by values. You might also use this to narrow values to display if you are using a shared query.
 
-- **Regex**: match a regex expression
-- **Is Null**: match if the value is null
-- **Is Not Null**: match if the value is not null
-- **Equal**: match if the value is equal to the specified value
-- **Different**: match if the value is different than the specified value
-- **Greater**\*: match if the value is greater than the specified value
-- **Lower**\*: match if the value is lower than the specified value
-- **Greater or equal**\*: match if the value is greater or equal
-- **Lower or equal**\*: match if the value is lower or equal
-- **Range**\*: match a range between a specified minimum and maximum, min and max included
+The available conditions for all fields are:
 
-\* Those conditions are only available for number fields.
+- **Regex:** Match a regex expression
+- **Is Null:** Match if the value is null
+- **Is Not Null:** Match if the value is not null
+- **Equal:** Match if the value is equal to the specified value
+- **Different:** match if the value is different than the specified value
+
+The available conditions for number fields are:
+
+- **Greater:** Match if the value is greater than the specified value
+- **Lower:** Match if the value is lower than the specified value
+- **Greater or equal:** Match if the value is greater or equal
+- **Lower or equal:** Match if the value is lower or equal
+- **Range:** Match a range between a specified minimum and maximum, min and max included
 
 Consider the following data set:
 

docs/sources/whatsnew/_index.md

@@ -11,24 +11,25 @@ as info on deprecations, breaking changes and plugin development read the [relea
 
 ## Grafana 7
 
-* [What's new in 7.3]({{< relref "whats-new-in-v7-3" >}})
-* [What's new in 7.2]({{< relref "whats-new-in-v7-2" >}})
-* [What's new in 7.1]({{< relref "whats-new-in-v7-1" >}})
-* [What's new in 7.0]({{< relref "whats-new-in-v7-0" >}})
+- [What's new in 7.4]({{< relref "whats-new-in-v7-4" >}})
+- [What's new in 7.3]({{< relref "whats-new-in-v7-3" >}})
+- [What's new in 7.2]({{< relref "whats-new-in-v7-2" >}})
+- [What's new in 7.1]({{< relref "whats-new-in-v7-1" >}})
+- [What's new in 7.0]({{< relref "whats-new-in-v7-0" >}})
 
 ## Grafana 6
-* [What's new in 6.7]({{< relref "whats-new-in-v6-7" >}})
-* [What's new in 6.6]({{< relref "whats-new-in-v6-6" >}})
-* [What's new in 6.5]({{< relref "whats-new-in-v6-5" >}})
-* [What's new in 6.4]({{< relref "whats-new-in-v6-4" >}})
-* [What's new in 6.3]({{< relref "whats-new-in-v6-3" >}})
-* [What's new in 6.2]({{< relref "whats-new-in-v6-2" >}})
-* [What's new in 6.1]({{< relref "whats-new-in-v6-1" >}})
-* [What's new in 6.0]({{< relref "whats-new-in-v6-0" >}})
+- [What's new in 6.7]({{< relref "whats-new-in-v6-7" >}})
+- [What's new in 6.6]({{< relref "whats-new-in-v6-6" >}})
+- [What's new in 6.5]({{< relref "whats-new-in-v6-5" >}})
+- [What's new in 6.4]({{< relref "whats-new-in-v6-4" >}})
+- [What's new in 6.3]({{< relref "whats-new-in-v6-3" >}})
+- [What's new in 6.2]({{< relref "whats-new-in-v6-2" >}})
+- [What's new in 6.1]({{< relref "whats-new-in-v6-1" >}})
+- [What's new in 6.0]({{< relref "whats-new-in-v6-0" >}})
 
 ## Grafana 5
-* [What's new in 5.4]({{< relref "whats-new-in-v5-4" >}})
-* [What's new in 5.3]({{< relref "whats-new-in-v5-3" >}})
-* [What's new in 5.2]({{< relref "whats-new-in-v5-2" >}})
-* [What's new in 5.1]({{< relref "whats-new-in-v5-1" >}})
-* [What's new in 5.0]({{< relref "whats-new-in-v5-0" >}})
+- [What's new in 5.4]({{< relref "whats-new-in-v5-4" >}})
+- [What's new in 5.3]({{< relref "whats-new-in-v5-3" >}})
+- [What's new in 5.2]({{< relref "whats-new-in-v5-2" >}})
+- [What's new in 5.1]({{< relref "whats-new-in-v5-1" >}})
+- [What's new in 5.0]({{< relref "whats-new-in-v5-0" >}})

docs/sources/whatsnew/whats-new-in-v7-4.md

++++
+title = "What's New in Grafana v7.4"
+description = "Feature and improvement highlights for Grafana v7.3"
+keywords = ["grafana", "new", "documentation", "7.3", "release notes"]
+aliases = ["/docs/grafana/latest/guides/whats-new-in-v7-3/"]
+weight = -31
+[_build]
+list = false
++++
+
+# What's new in Grafana v7.4
+
+This topic includes the release notes for Grafana v7.4 beta. For all details, read the full [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md).
+
+## Grafana OSS features
+
+These features are included in the Grafana Enterprise edition software.
+
+### Beta Time series panel visualization
+
+Grafana 7.4 brings the beta version of the next-gen graph visualization. The new graph panel, the _Time series_ visualization, is high-performance visualization based on the uPlot library. This new graph visualization uses the new panel architecture introduced in Grafana 7.0 and integrates with field options, overrides, and transformations.
+
+The Time series beta panel implements the majority of the functionalities available in the current Graph panel. Our plan is to have close to full coverage of the features in Grafana 8.0, coming later this year.
+
+Apart from major performance improvements, the new Time series panel implements new features like line interpolation modes, support for more than two Y-axes, soft min and max axis limits, automatic points display based on data density, and gradient fill modes.
+
+### Beta Node graph panel visualization
+
+_Node graph_ is a new panel type that can visualize directed graphs or network in dashboards, but also in Explore. It uses directed force layout to effectively position the nodes so it can help with displaying complex infrastructure maps, hierarchies, or execution diagrams.
+
+All the information and stats shown in the Node graph beta are driven by the data provided in the response from the data source. The first data source that is using this panel is AWS X-Ray, for displaying their service map data.
+
+For more details about how to use the X-Ray service map feature, see the [X-Ray plugin documentation](https://grafana.com/grafana/plugins/grafana-x-ray-datasource).
+
+### New transformations
+
+The following transformations were added in Grafana 7.4.
+
+#### Sort by transformation
+
+The _Sort by_ transformation allows you to sort data before sending it to the visualization.
+
+For more information, refer to [Filter data by value]({{< relref "../panels/transformations/types-options.md#sort-by" >}}) in [Transformation types and options]({{< relref "../panels/transformations/types-options.md" >}}).
+
+#### Filter data by value transform
+
+The new _Filter data by value_ transformation allows you to filter your data directly in Grafana and remove some data points from your query result.
+
+This transformation is very useful if your data source does not natively filter by values. You might also use this to narrow values to display if you are using a shared query.
+
+For more information, refer to [Filter data by value]({{< relref "../panels/transformations/types-options.md#filter-data-by-value" >}}) in [Transformation types and options]({{< relref "../panels/transformations/types-options.md" >}}).
+
+### Exemplar support
+
+Grafana graphs now support Prometheus exemplars. They are displayed as diamonds in the graph visualization.
+
+> **Note:** Support for exemplars will be added in version Prometheus 2.25+,
+
+![Exemplar example](/img/docs/v74/exemplars.png)
+
+### Trace to logs
+
+You can now navigate from a span in a trace view directly to logs relevant for that span. This feature is available for the Tempo, Jaeger, and Zipkin data sources.
+
+The following topics were updated as a result of this feature:
+
+- [Explore]({{< relref "../explore/index.md#trace-to-logs" >}})
+- [Jaeger]({{< relref "../datasources/jaeger.md#trace-to-logs" >}})
+- [Tempo]({{< relref "../datasources/tempo.md#trace-to-logs" >}})
+- [Zipkin]({{< relref "../datasources/zipkin.md#trace-to-logs" >}})
+
+### Server-side expressions
+
+_Server-side expressions_ is an experimental feature that allows you to manipulate data returned from backend data source queries. Expressions allow you to manipulate data with math and other operations when the data source is a backend data source or a **--Mixed--** data source.
+
+The main use case is for [multi-dimensional](https://grafana.com/docs/grafana/latest/getting-started/timeseries-dimensions/#time-series-dimensions) data sources used with the upcoming next generation alerting, but expressions can be used with backend data sources and visualization as well.
+
+> **Note:** Queries built with this feature may break with minor version upgrades until Grafana 8 is released.
+
+### Variable support in alert notifications
+
+You can now provide detailed information to alert notification recipients by injecting alert query data into an alert notification. Labels that exist from the evaluation of the alert query can be used in the alert rule name and in the alert notification message fields. The alert label data is injected into the notification fields when the alert is in the alerting state. When there are multiple unique values for the same label, the values are comma-separated.
+
+![Variable support in alert notifications](/img/docs/v74/alert-variable-notifications.png)
+
+### Content security policy support
+
+We have added support for [Content Security Policy (CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP), a layer of security that helps detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks.
+
+CSP support is disabled by default, to enable it you must set `content_security_policy = true` in the Grafana configuration. If enabling it, you should also review, and potentially tweak, the CSP header template, via the configuration setting `content_security_policy_template`.
+
+You can lock down what can be done in the frontend code. Lock down what can be loaded, what JavaScript is executed. Not compatible with some plugins.
+
+### Elasticsearch data source updates
+
+Grafana 7.4 includes the following enhancements
+
+- Added support for serial differencing pipeline aggregation.
+- Added support for moving function pipeline aggregation.
+- Added support to the terms aggregation for ordering by percentiles and extended stats.
+- Updated date histogram auto interval handling for alert queries.
+
+> **Note:** We have deprecated browser access mode. Iit will be removed in a future release.
+
+### Azure Monitor updates
+
+The Azure Monitor query type was renamed to Metrics and Azure Logs Analytics was renamed to Logs to match the service names in Azure and align the concepts with the rest of Grafana.
+
+[Azure Monitor]({{< relref "../datasources/azuremonitor.md" >}}) was updated to reflect this change.
+
+### MQL support added for Google Cloud Monitoring
+
+You can now use Monitoring Query Language (MQL) for querying time-series data. MQL provides an expressive, text-based interface to retrieve, filter, and manipulate time-series data.
+
+Unlike the visual query builder, MQL allows you to control the time range and period of output data, create new labels to aggregate data, compute the ratio of current values to past values, and so on.
+
+MQL uses a set of operations and functions. Operations are linked together using the common pipe mechanism, where the output of one operation becomes the input to the next. Linking operations makes it possible to build up complex queries incrementally.
+
+Once query type Metrics is selected in the Cloud Monitoring query editor, you can toggle between the editor modes for visual query builder and MQL.
+
+Many thanks to [mtanda](https://github.com/mtanda) this contribution!
+
+### Query Editor Help
+
+The feature previously referred to as DataSource Start Pages or Cheat Sheets has been renamed to Query Editor Help, and is now supported in panel query editors (depending on the data source), as well as in Explore.
+### Inspecting variables and their dependencies
+The variables list has an additional column indicating whether variables are referenced in queries and panel names or not. The dependencies graph provides an easy way to check variable dependencies. You can click on a variable name within the graph to make updates to the variable as needed. 
+## Grafana Enterprise features
+
+These features are included in the Grafana Enterprise edition software.
+
+### Licensing changes
+
+When determining a user’s role for billing purposes, a user who has the ability to edit and save dashboards is considered an Editor. This includes any user who is an Editor or Admin at the Org level, and who has granted Admin or Edit permissions via [Dashboard and folder permissions]({{< relref "../permissions/dashboard_folder_permissions.md">}}).
+
+After the number of Viewers or Editors has reached its license limit, only Admins will see a banner in Grafana indicating that the license limit has been reached. Previously, all users saw the banner.
+
+Grafana Enterprise license tokens update automatically on a daily basis, which means you no longer need to manually update your license, and the process for adding additional users to a license is smoother than it was before.
+
+### Export usage insights to Loki
+
+You can now export usage insights logs to Loki and query them from Grafana. Usage insights logs include dashboard visits, data source views, queries and errors, and more.
+
+### New audit log events
+
+A counter for audit log writing actions with status (success / failure) and logger (loki / file / console) labels was added.
+A `sessionId` field to all auditing logs was added because it is useful to understand which session was logged out of.
+
+### Reports support Unicode
+
+You can now select a font, other than the default, for Unicode-based scripts. As a result, an automatically generated PDF of a dashboard, which contains for example Chinese or Cyrillic text, can display them. Because the size of a report increases as additional fonts are added, this feature is not on by default.
+
+## Breaking changes
+
+### Plugin compatibility
+
+We have upgraded AngularJS from version 1.6.6 to 1.8.2. Due to this upgrade some old angular plugins might stop working and will require a small update. This is due to the deprecation and removal of pre-assigned bindings. So if your custom angular controllers expect component bindings in the controller constructor you need to move this code to an $onInit function. For more details on how to migrate AngularJS code open the migration guide and search for pre-assigning bindings.
+
+In order not to break all angular panel plugins and data sources we have some custom angular inject behavior that makes sure that bindings for these controllers are still set before constructor is called so many old angular panels and data source plugins will still work.
+
+### Fixes Constant variable persistence confusion
+
+In order to minimize the confusion with Constant variable usage, we've removed the ability to make Constant variables visible. This change will also migrate all existing visible Constant variables to Textbox variables because which we think this is a more appropriate type of variable for this use case.
+
+## Upgrading
+
+See [upgrade notes]({{< relref "../installation/upgrading.md" >}}).
+
+## Changelog
+
+Check out [CHANGELOG.md](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) for a complete list of new features, changes, and bug fixes.