* Set every page to have defaults of 'Enterprise' and 'Open source' labels Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration pages to have of 'Cloud', 'Enterprise', and 'Open source' labels Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration/enterprise-licensing pages to have 'Enterprise' labels Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration/organization-management pages to have 'Enterprise' and 'Open source' labels Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration/provisioning pages to have 'Enterprise' and 'Open source' labels Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration/recorded-queries pages to have labels cloud,enterprise * Set administration/roles-and-permissions/access-control pages to have labels cloud,enterprise Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set administration/stats-and-license pages to have labels cloud,enterprise * Set alerting pages to have labels cloud,enterprise,oss * Set breaking-changes pages to have labels cloud,enterprise,oss * Set dashboards pages to have labels cloud,enterprise,oss * Set datasources pages to have labels cloud,enterprise,oss * Set explore pages to have labels cloud,enterprise,oss * Set fundamentals pages to have labels cloud,enterprise,oss * Set introduction/grafana-cloud pages to have labels cloud Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix introduction pages products Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set panels-visualizations pages to have labels cloud,enterprise,oss * Set release-notes pages to have labels cloud,enterprise,oss * Set search pages to have labels cloud,enterprise,oss * Set setup-grafana/configure-security/audit-grafana pages to have labels cloud,enterprise Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set setup-grafana/configure-security/configure-authentication pages to have labels cloud,enterprise,oss * Set setup-grafana/configure-security/configure-authentication/enhanced-ldap pages to have labels cloud,enterprise * Set setup-grafana/configure-security/configure-authentication/saml pages to have labels cloud,enterprise * Set setup-grafana/configure-security/configure-database-encryption/encrypt-secrets-using-hashicorp-key-vault pages to have labels cloud,enterprise * Set setup-grafana/configure-security/configure-request-security pages to have labels cloud,enterprise,oss Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set setup-grafana/configure-security/configure-team-sync pages to have labels cloud,enterprise Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set setup-grafana/configure-security/export-logs pages to have labels cloud,enterprise Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Set troubleshooting pages to have labels cloud,enterprise,oss * Set whatsnew pages to have labels cloud,enterprise,oss * Apply updated labels from review Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com> Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>
5.8 KiB
aliases | description | keywords | labels | title | weight | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Export logs of usage insights |
|
|
Export logs of usage insights | 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. {{% /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.
Usage insights logs
Usage insights logs are JSON objects that represent certain user activities, such as:
- A user opens a dashboard.
- A query is sent to a data source.
Scope
A log is created every time a user opens a dashboard or when a query is sent to a data source in the dashboard view. A query that is performed via Explore does not generate a log.
Format
Logs of usage insights contain the following fields, where the fields followed by * are always available, and the others depend on the logged event:
Field name | Type | Description |
---|---|---|
eventName * |
string | Type of the event, which can be either data-request or dashboard-view . |
folderName * |
string | Name of the dashboard folder. |
dashboardName * |
string | Name of the dashboard where the event happened. |
dashboardId * |
number | ID of the dashboard where the event happened. |
datasourceName |
string | Name of the data source that was queried. |
datasourceType |
string | Type of the data source that was queried. For example, prometheus , elasticsearch , or loki . |
datasourceId |
number | ID of the data source that was queried. |
panelId |
number | ID of the panel of the query. |
panelName |
string | Name of the panel of the query. |
error |
string | Error returned by the query. |
duration |
number | Duration of the query. |
source |
string | Source of the query. For example, dashboard or explore . |
orgId * |
number | ID of the user’s organization. |
orgName * |
string | Name of the user’s organization. |
timestamp * |
string | The date and time that the request was made, in Coordinated Universal Time (UTC) in RFC3339 format. |
tokenId * |
number | ID of the user’s authentication token. |
username * |
string | Name of the Grafana user that made the request. |
userId * |
number | ID of the Grafana user that made the request. |
totalQueries * |
number | Number of queries executed for the data request. |
cachedQueries * |
number | Number of fetched queries that came from the cache. |
Configuration
To export your logs, enable the usage insights feature and [configure]({{< relref "../../setup-grafana/configure-grafana" >}}) an export location in the configuration file:
[usage_insights.export]
# Enable the usage insights export feature
enabled = true
# Storage type
storage = loki
The options for storage type are loki
and logger
(added in Grafana Enterprise 8.2).
If the storage type is set to loki
you'll need to also configure Grafana
to export to a Loki ingestion server. To do this, you'll need Loki installed.
Refer to Install Loki for instructions
on how to install Loki.
[usage_insights.export.storage.loki]
# Set the communication protocol to use with Loki (can be grpc or http)
type = grpc
# Set the address for writing logs to Loki (format must be host:port)
url = localhost:9095
# Defaults to true. If true, it establishes a secure connection to Loki
tls = true
# Set the tenant ID for Loki communication, which is disabled by default.
# The tenant ID is required to interact with Loki running in multi-tenant mode.
tenant_id =
Using logger
will print usage insights to your [Grafana server log]({{< relref "../../setup-grafana/configure-grafana#log" >}}).
There is no option for configuring the logger
storage type.
Visualize Loki usage insights in Grafana
If you export logs into Loki, you can build Grafana dashboards to understand your Grafana instance usage.
- Add Loki as a data source. Refer to Grafana fundamentals tutorial.
- Import one of the following dashboards:
- Play with usage insights to understand them:
- In Explore, you can use the query
{datasource="gdev-loki",kind="usage_insights"}
to retrieve all logs related to yourgdev-loki
data source. - In a dashboard, you can build a table panel with the query
topk(10, sum by (error) (count_over_time({kind="usage_insights", datasource="gdev-prometheus"} | json | error != "" [$__interval])))
to display the 10 most common errors your users see using thegdev-prometheus
data source. - In a dashboard, you can build a graph panel with the queries
sum by(host) (count_over_time({kind="usage_insights"} | json | eventName="data-request" | error != "" [$__interval]))
andsum by(host) (count_over_time({kind="usage_insights"} | json | eventName="data-request" | error = "" [$__interval]))
to show the evolution of the data request count over time. Usingby (host)
allows you to have more information for each Grafana server you have if you have set up Grafana for [high availability](<{{< relref "../../setup-grafana/set-up-for-high-availability/" >}}>).
- In Explore, you can use the query