Docs: initial pruning of outdated versioning info (#95212)
* initial pruning of outdated versioning info * removing erroneous file
This commit is contained in:
Jacob Valdez
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user