View server on Grafana Labs

Internal Grafana metrics

Sat, 04 Apr 2026 12:26:57 +0000

Internal Grafana metrics

Grafana collects some metrics about itself internally. Grafana supports pushing metrics to Graphite or exposing them to be scraped by Prometheus.

For more information about configuration options related to Grafana metrics, refer to metrics and metrics.graphite in Configuration.

Available metrics

When enabled, Grafana exposes a number of metrics, including:

Active Grafana instances
Number of dashboards, users, and playlists
HTTP status codes
Requests by routing group
Grafana active alerts
Grafana performance

Pull metrics from Grafana into Prometheus

These instructions assume you have already added Prometheus as a data source in Grafana.

Enable Prometheus to scrape metrics from Grafana. In your configuration file (grafana.ini or custom.ini depending on your operating system) remove the semicolon to enable the following configuration options:

# Metrics available at HTTP URL /metrics and /metrics/plugins/:pluginId
[metrics]
# Disable / Enable internal metrics
enabled           = true

# Disable total stats (stat_totals_*) metrics to be generated
disable_total_stats = false

(optional) If you want to require authorization to view the metrics endpoints, then uncomment and set the following options:
```
basic_auth_username =
basic_auth_password =
```
Restart Grafana. Grafana now exposes metrics at http://localhost:3000/metrics.

Add the job to your prometheus.yml file. Example:

- job_name: 'grafana_metrics'

   scrape_interval: 15s
   scrape_timeout: 5s

   static_configs:
     - targets: ['localhost:3000']

Restart Prometheus. Your new job should appear on the Targets tab.
In Grafana, hover your mouse over the Configuration (gear) icon on the left sidebar and then click Data Sources.
Select the Prometheus data source.
On the Dashboards tab, Import the Grafana metrics dashboard. All scraped Grafana metrics are available in the dashboard.

View Grafana metrics in Graphite

These instructions assume you have already added Graphite as a data source in Grafana.

Enable sending metrics to Graphite. In your configuration file (grafana.ini or custom.ini depending on your operating system) remove the semicolon to enable the following configuration options:

# Metrics available at HTTP API Url /metrics
[metrics]
# Disable / Enable internal metrics
enabled           = true

# Disable total stats (stat_totals_*) metrics to be generated
disable_total_stats = false

Enable [metrics.graphite] options:

# Send internal metrics to Graphite
[metrics.graphite]
# Enable by setting the address setting (ex localhost:2003)
address = <hostname or ip>:<port#>
prefix = prod.grafana.%(instance_name)s.

Restart Grafana. Grafana now exposes metrics at http://localhost:3000/metrics and sends them to the Graphite location you specified.

Pull metrics from Grafana backend plugin into Prometheus

Any installed backend plugin exposes a metrics endpoint through Grafana that you can configure Prometheus to scrape.

These instructions assume you have already added Prometheus as a data source in Grafana.

Enable Prometheus to scrape backend plugin metrics from Grafana. In your configuration file (grafana.ini or custom.ini depending on your operating system) remove the semicolon to enable the following configuration options:

# Metrics available at HTTP URL /metrics and /metrics/plugins/:pluginId
[metrics]
# Disable / Enable internal metrics
enabled           = true

# Disable total stats (stat_totals_*) metrics to be generated
disable_total_stats = false

(optional) If you want to require authorization to view the metrics endpoints, then uncomment and set the following options:
```
basic_auth_username =
basic_auth_password =
```
Restart Grafana. Grafana now exposes metrics at http://localhost:3000/metrics/plugins/<plugin id>, e.g. http://localhost:3000/metrics/plugins/grafana-github-datasource if you have the Grafana GitHub datasource installed.

Add the job to your prometheus.yml file. Example:

- job_name: 'grafana_github_datasource'

   scrape_interval: 15s
   scrape_timeout: 5s
   metrics_path: /metrics/plugins/grafana-test-datasource

   static_configs:
     - targets: ['localhost:3000']

Restart Prometheus. Your new job should appear on the Targets tab.
In Grafana, hover your mouse over the Configuration (gear) icon on the left sidebar and then click Data Sources.
Select the Prometheus data source.
Import a Golang application metrics dashboard - for example Go Processes.

View server settings

Sat, 04 Apr 2026 12:26:57 +0000

View Grafana server settings

Refer to Fine-grained access control in Grafana Enterprise to understand how you can control access with fine-grained permissions.

If you are a Grafana server administrator, use the Settings tab to view the settings that are applied to your Grafana server via the Configuration file and any environmental variables.

Note: Only Grafana server administrators can access the Server Admin menu. For more information about about administrative permissions, refer to Grafana server admin.

View server settings

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Hover your cursor over the Server Admin (shield) icon in the side menu and then click the Settings tab.

Available settings

For a full list of server settings, refer to Configuration.

View server stats

Sat, 04 Apr 2026 12:26:57 +0000

View Grafana server stats

Refer to Fine-grained access control in Grafana Enterprise to understand how you can control access with fine-grained permissions.

If you are a Grafana server admin, then you can view useful statistics about your Grafana server in the Stats & Licensing tab.

Note: Only Grafana server administrators can access the Server Admin menu. For more information about about administrative permissions, refer to Grafana server admin.

View server stats

Log in to your Grafana server with an account that has the Grafana Admin flag set.
Hover your cursor over the Server Admin (shield) icon in the side menu and then click the Stats & Licensing tab.

Available stats

The following statistics are displayed in the Stats tab:

Total users Note: Total users = Total admins + Total editors + Total viewers
Total admins
Total editors
Total viewers
Active users (seen last 30 days) Note: Active users = Active admins + Active editors + Active viewers
Active admins (seen last 30 days)
Active editors (seen last 30 days)
Active viewers (seen last 30 days)
Active sessions
Total dashboards
Total orgs
Total playlists
Total snapshots
Total dashboard tags
Total starred dashboards
Total alerts

Counting users

If a user belongs to several organizations, then that user is counted once as a user in the highest organization role they are assigned, regardless of how many organizations the user belongs to.

For example, if Sofia is a Viewer in two organizations, an Editor in two organizations, and Admin in three organizations, then she would be reflected in the stats as:

Total users 1
Total admins 1