Grafana EnterpriseAuditing


Note: Only available in Grafana Enterprise v7.3+.

Auditing allows you to track important changes to your Grafana instance. By default, audit logs are logged to file but the auditing feature also supports sending logs directly to Loki.

Audit logs

Audit logs are JSON objects representing user actions like:

  • Modifications ro resources such as dashboards and data sources.
  • A user failing to log in.


Audit logs contain the following fields. The fields followed by * are always available, the others depends on the type of action logged.

Field name Type Description
timestamp* string The date and time the request was made, in coordinated universal time (UTC) using the RFC3339 format.
user* object Information about the user that made the request. At least one of the UserID / ApiKeyID fields will not be empty if isAnonymous=false.
user.userId number ID of the Grafana user that made the request.
user.orgId* number Current organization of the user that made the request.
user.orgRole string Current role of the user that made the request. string Name of the Grafana user that made the request.
user.apiKeyId number ID of the Grafana API key used to make the request.
user.isAnonymous* boolean true if an anonymous user made the request, false otherwise.
action* string The request action (eg. create, update, manage-permissions).
request* object Information about the HTTP request.
request.params object Request path parameters.
request.query object Request query parameters.
request.body string Request body.
result* object Information about the HTTP response.
result.statusType* string success if the request action was successful, failure otherwise.
result.statusCode number HTTP status of the request.
result.failureMessage string HTTP error message.
result.body string Response body.
resources array Information about the resources that the request action impacted. Can be null for non-resource actions like login and logout.
resources[x].id* number ID of the resource.
resources[x].type* string Type of the resource (logged resources are: alert, alert-notification, annotation, api-key, auth-token, dashboard, datasource, folder, org, panel, playlist, report, team, user, version).
requestUri* string Request URI.
ipAddress* string IP address that the request was made from.
userAgent* string Agent through which the request was made.
grafanaVersion* string Grafana current version when this log is created.
additionalData object Provide additional information on the request. For now, it’s only used in login actions to log external user information if an external system was used to log in.

Recorded actions

The audit logs include records about the following categories of actions:


  • Log in.
  • Log out.
  • Revoke a user authentication token.
  • Create or delete an API key.

User management

  • Create, update, or delete a user.
  • Enable or disable a user.
  • Manage user role and permissions.
  • LDAP sync or information access.

Team and organization management

  • Create, update, or delete a team or organization.
  • Add or remove a member of a team or organization.
  • Manage organization members roles.
  • Manage team members permissions.
  • Invite an external member to an organization.
  • Revoke a pending invitation to an organization.
  • Add or remove an external group to sync with a team.

Folder and dashboard management

  • Create, update, or delete a folder.
  • Manage folder permissions.
  • Create, import, update, or delete a dashboard.
  • Restore an old dashboard version.
  • Manage dashboard permissions.

Data sources management

  • Create, update, or delete a data source.
  • Manage data source permissions.

Alerts and notification channels management

  • Create, update, or delete a notification channel.
  • Test an alert or a notification channel.
  • Pause an alert.


  • Create, update, or delete a report.
  • Update reporting settings.
  • Send reporting email.

Annotations, playlists and snapshots management

  • Create, update, or delete an annotation.
  • Create, update, or delete a playlist.
  • Create or delete a snapshot.


Note: The auditing feature is disabled by default.

Audit logs can be saved into files, sent to a Loki instance or sent to the Grafana default logger. By default, only the file exporter is enabled. You can choose which exporter to use in the configuration file.

Options are file, loki, and console. Use spaces to separate multiple modes, such as file loki.

By default, when a user create or update a dashboard, its content will not appear in the logs as it can significantly increase the size of your logs. If this is important information for you and you can handle the amount of data generated, then you can enable this option in the configuration.

# Enable the auditing feature
enabled = false
# List of enabled loggers
loggers = file
# Keep dashboard content in the logs (request or response fields); this can significantly increase the size of your logs.
log_dashboard_content = false

Each exporter has its own configuration fields.

File exporter

Audit logs are saved into files. You can configure the folder to use to save these files. Logs are rotated when the file size is exceeded and at the start of a new day.

# Path to logs folder
path = data/log
# Maximum log files to keep
max_files = 5
# Max size in megabytes per log file
max_file_size_mb = 256

Loki exporter

Audit logs are sent to a Loki service.

# Set the URL for writing logs to Loki
url = localhost:9095
# Defaults to true. If true, it establishes a secure connection to Loki
tls = true

If you have multiple Grafana instances sending logs to the same Loki service or if you are using Loki for non-audit logs, audit logs come with additional labels to help identifying them:

  • host - OS hostname on which the Grafana instance is running.
  • grafana_instance - Application URL.
  • kind - auditing

Console exporter

Audit logs are sent to the Grafana default logger. The audit logs use the auditing.console logger and are logged on debug-level, learn how to enable debug logging in the log configuration section of the documentation. Accessing the audit logs in this way is not recommended for production use.