Documentation Grafana documentation Alerting Additional configuration Configure alert state history

Configure alert state history

Starting with Grafana 10, Alerting can record all alert rule state changes for your Grafana managed alert rules in a Loki instance.

This allows you to explore the behavior of your alert rules in the Grafana explore view and levels up the existing state history dialog box with a powerful new visualisation.

Configuring Loki

To set up alert state history, make sure to have a Loki instance Grafana can write data to. The default settings might need some tweaking as the state history dialog box might query up to 30 days of data.

The following change to the default configuration should work for most instances, but look at the full Loki configuration settings and adjust according to your needs.

As this might impact the performances of an existing Loki instance, use a separate Loki instance for the alert state history.

yaml Copy

limits_config:
  split_queries_by_interval: '24h'
  max_query_parallelism: 32

Configuring Grafana

Additional configuration is required in the Grafana configuration file to have it working with the alert state history.

The example below instructs Grafana to write alert state history to a local Loki instance:

toml Copy

[unified_alerting.state_history]
enabled = true
backend = "loki"
loki_remote_url = "http://localhost:3100"

[feature_toggles]
enable = alertStateHistoryLokiSecondary, alertStateHistoryLokiPrimary, alertStateHistoryLokiOnly

Adding the Loki data source

Refer to the instructions on adding a data source.

Querying the history

If everything is set up correctly you can use the Grafana Explore view to start querying the Loki data source.

A simple litmus test to see if data is being written correctly into the Loki instance is the following query:

logQL Copy

{ from="state-history" } | json