Docs: initial pruning of outdated versioning info (#95212)
* initial pruning of outdated versioning info * removing erroneous file
This commit is contained in:
@@ -93,10 +93,6 @@ export GF_FEATURE_TOGGLES_ENABLE=newNavigation
|
||||
|
||||
## Variable expansion
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Only available in Grafana 7.1+.
|
||||
{{% /admonition %}}
|
||||
|
||||
If any of your options contains the expression `$__<provider>{<argument>}`
|
||||
or `${<environment variable>}`, then they will be processed by Grafana's
|
||||
variable expander. The expander runs the provider with the provided argument
|
||||
@@ -768,7 +764,7 @@ Number dashboard versions to keep (per dashboard). Default: `20`, Minimum: `1`.
|
||||
This feature prevents users from setting the dashboard refresh interval to a lower value than a given interval value. The default interval value is 5 seconds.
|
||||
The interval string is a possibly signed sequence of decimal numbers, followed by a unit suffix (ms, s, m, h, d), e.g. `30s` or `1m`.
|
||||
|
||||
As of Grafana v7.3, this also limits the refresh interval options in Explore.
|
||||
This also limits the refresh interval options in Explore.
|
||||
|
||||
### default_home_dashboard_path
|
||||
|
||||
@@ -1069,14 +1065,10 @@ Limit of API key seconds to live before expiration. Default is -1 (unlimited).
|
||||
|
||||
### sigv4_auth_enabled
|
||||
|
||||
> Only available in Grafana 7.3+.
|
||||
|
||||
Set to `true` to enable the AWS Signature Version 4 Authentication option for HTTP-based datasources. Default is `false`.
|
||||
|
||||
### sigv4_verbose_logging
|
||||
|
||||
> Only available in Grafana 8.4+.
|
||||
|
||||
Set to `true` to enable verbose request signature logging when AWS Signature Version 4 Authentication is enabled. Default is `false`.
|
||||
|
||||
<hr />
|
||||
@@ -1481,8 +1473,6 @@ Syslog tag. By default, the process's `argv[0]` is used.
|
||||
|
||||
## [log.frontend]
|
||||
|
||||
**Note:** This feature is available in Grafana 7.4+.
|
||||
|
||||
### enabled
|
||||
|
||||
Faro javascript agent is initialized. Default is `false`.
|
||||
|
||||
@@ -32,9 +32,9 @@ With custom branding, you have the ability to modify the following elements:
|
||||
- Side menu top logo
|
||||
- Footer and help menu links
|
||||
- Fav icon (shown in browser tab)
|
||||
- Login title (will not appear if a login logo is set, Grafana v7.0+)
|
||||
- Login subtitle (will not appear if a login logo is set, Grafana v7.0+)
|
||||
- Login box background (Grafana v7.0+)
|
||||
- Login title (will not appear if a login logo is set)
|
||||
- Login subtitle (will not appear if a login logo is set)
|
||||
- Login box background
|
||||
- Loading logo
|
||||
|
||||
> You will have to host your logo and other images used by the custom branding feature separately. Make sure Grafana can access the URL where the assets are stored.
|
||||
|
||||
@@ -23,20 +23,12 @@ Defaults to `<paths.data>/license.jwt`.
|
||||
|
||||
### license_text
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana Enterprise version 7.4 and later.
|
||||
{{% /admonition %}}
|
||||
|
||||
When set to the text representation (i.e. content of the license file)
|
||||
of the license, Grafana will evaluate and apply the given license to
|
||||
the instance.
|
||||
|
||||
### auto_refresh_license
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana Enterprise version 7.4 and later.
|
||||
{{% /admonition %}}
|
||||
|
||||
When enabled, Grafana will send the license and usage statistics to
|
||||
the license issuer. If the license has been updated on the issuer's
|
||||
side to be valid for a different number of users or a new duration,
|
||||
@@ -45,10 +37,6 @@ automatically. Defaults to `true`.
|
||||
|
||||
### license_validation_type
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana Enterprise version 8.3 and later.
|
||||
{{% /admonition %}}
|
||||
|
||||
When set to `aws`, Grafana will validate its license status with Amazon Web Services (AWS) instead of with Grafana Labs. Only use this setting if you purchased an Enterprise license from AWS Marketplace. Defaults to empty, which means that by default Grafana Enterprise will validate using a license issued by Grafana Labs. For details about licenses issued by AWS, refer to [Activate a Grafana Enterprise license purchased through AWS Marketplace]({{< relref "../../../administration/enterprise-licensing/activate-aws-marketplace-license" >}}).
|
||||
|
||||
## [white_labeling]
|
||||
@@ -368,10 +356,6 @@ New duration for renewed tokens. Vault may be configured to ignore this value an
|
||||
|
||||
## [security.egress]
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana Enterprise version 7.4 and later.
|
||||
{{% /admonition %}}
|
||||
|
||||
Security egress makes it possible to control outgoing traffic from the Grafana server.
|
||||
|
||||
### host_deny_list
|
||||
@@ -398,10 +382,6 @@ Encryption algorithm used to encrypt secrets stored in the database and cookies.
|
||||
|
||||
## [caching]
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in Grafana Enterprise version 7.5 and later.
|
||||
{{% /admonition %}}
|
||||
|
||||
When query caching is enabled, Grafana can temporarily store the results of data source queries and serve cached responses to similar requests.
|
||||
|
||||
### backend
|
||||
|
||||
@@ -26,7 +26,7 @@ To enable sending Grafana Cloud audit logs to your Grafana Cloud Logs instance,
|
||||
Only API requests or UI actions that trigger an API request generate an audit log.
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) version 7.3 and later, and [Grafana Cloud](/docs/grafana-cloud).
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) and [Grafana Cloud](/docs/grafana-cloud).
|
||||
{{% /admonition %}}
|
||||
|
||||
## Audit logs
|
||||
|
||||
-2
@@ -361,8 +361,6 @@ configuring Azure AD authentication in Grafana.
|
||||
|
||||
### Users with over 200 Group assignments
|
||||
|
||||
> Supported in Grafana v8.5 and later versions.
|
||||
|
||||
To ensure that the token size doesn't exceed HTTP header size limits,
|
||||
Entra ID limits the number of object IDs that it includes in the groups claim.
|
||||
If a user is member of more groups than the
|
||||
|
||||
+1
-1
@@ -47,7 +47,7 @@ a user as member of a team, and it will not be removed when the user signs in. T
|
||||
|
||||
In the open source version of Grafana, user data from LDAP is synchronized only during the login process when authenticating using LDAP.
|
||||
|
||||
With active LDAP synchronization, available in Grafana Enterprise version 6.3 and later, you can configure Grafana to actively sync users with LDAP servers in the background. Only users that have logged into Grafana at least once are synchronized.
|
||||
With active LDAP synchronization, you can configure Grafana to actively sync users with LDAP servers in the background. Only users that have logged into Grafana at least once are synchronized.
|
||||
|
||||
Users with updated role and team membership will need to refresh the page to get access to the new features.
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ Request security allows you to limit requests from the Grafana server by targeti
|
||||
This can be used to limit access to internal systems that the server Grafana runs on can access but that users of Grafana should not be able to access. This feature does not affect traffic from the Grafana users browser.
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) version 7.4 and later, and [Grafana Cloud Pro and Advanced](/docs/grafana-cloud/).
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) and [Grafana Cloud Pro and Advanced](/docs/grafana-cloud/).
|
||||
{{% /admonition %}}
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
|
||||
@@ -21,7 +21,7 @@ Team sync lets you set up synchronization between your auth providers teams and
|
||||
Grafana keeps track of all synchronized users in teams, and you can see which users have been synchronized in the team members list, see `LDAP` label in screenshot.
|
||||
This mechanism allows Grafana to remove an existing synchronized user from a team when its group membership changes. This mechanism also enables you to manually add a user as member of a team, and it will not be removed when the user signs in. This gives you flexibility to combine LDAP group memberships and Grafana team memberships.
|
||||
|
||||
> Currently the synchronization only happens when a user logs in, unless LDAP is used with the active background synchronization that was added in Grafana 6.3.
|
||||
> Currently the synchronization only happens when a user logs in, unless LDAP is used with the active background synchronization.
|
||||
|
||||
<div class="clearfix"></div>
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ weight: 900
|
||||
# Export logs of usage insights
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) version 7.4 and later, and [Grafana Cloud Pro and Advanced](/docs/grafana-cloud/).
|
||||
Available in [Grafana Enterprise]({{< relref "../../introduction/grafana-enterprise" >}}) and [Grafana Cloud Pro and Advanced](/docs/grafana-cloud/).
|
||||
{{% /admonition %}}
|
||||
|
||||
By exporting usage logs to Loki, you can directly query them and create dashboards of the information that matters to you most, such as dashboard errors, most active organizations, or your top-10 most-used queries. This configuration is done for you in Grafana Cloud, with provisioned dashboards. Read about them in the [Grafana Cloud documentation](/docs/grafana-cloud/usage-insights/).
|
||||
|
||||
@@ -136,7 +136,7 @@ Service account access tokens inherit permissions from the service account.
|
||||
### API keys
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
If you use Grafana v8.5 or newer, you should use service accounts instead of API keys. API keys will be deprecated in the near future. For more information, refer to [Grafana service accounts]({{< relref ".#service-accounts" >}}).
|
||||
Grafana recommends using service accounts instead of API keys. API keys will be deprecated in the near future. For more information, refer to [Grafana service accounts]({{< relref ".#service-accounts" >}}).
|
||||
{{% /admonition %}}
|
||||
|
||||
You can use Grafana API keys to interact with data sources via HTTP APIs.
|
||||
|
||||
@@ -35,7 +35,7 @@ Alert notifications can include images, but rendering many images at the same ti
|
||||
## Install Grafana Image Renderer plugin
|
||||
|
||||
{{% admonition type="note" %}}
|
||||
Starting from Grafana v7.0.0, all PhantomJS support has been removed. Please use the Grafana Image Renderer plugin or remote rendering service.
|
||||
All PhantomJS support has been removed. Instead, use the Grafana Image Renderer plugin or remote rendering service.
|
||||
{{% /admonition %}}
|
||||
|
||||
To install the plugin, refer to the [Grafana Image Renderer Installation instructions](/grafana/plugins/grafana-image-renderer/?tab=installation#installation).
|
||||
|
||||
@@ -19,9 +19,7 @@ weight: 1100
|
||||
|
||||
# Set up Grafana Live
|
||||
|
||||
Grafana Live is a real-time messaging engine introduced in Grafana v8.0.
|
||||
|
||||
With Grafana Live, you can push event data to a frontend as soon as an event occurs.
|
||||
Grafana Live is a real-time messaging engine you can use to push event data to a frontend as soon as an event occurs.
|
||||
|
||||
This could be notifications about dashboard changes, new frames for rendered data, and so on. Live features can help eliminate a page reload or polling in many places, it can stream Internet of things (IoT) sensors or any other real-time data to panels.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user