Grafana version : Grafana v13.0.1 (a100054f) Noticed this error of late. <30>1 2026-05-04T10:59:40.20063-04:00 raspberry05 grafana 247674 - - logger=ngalert.state.historian backend=annotations rule_uid=cf50q8nv3ooaoe org_id=1 t=2026-05-04T10:59:40.200174121-04:00 level=error msg=“Failed to save hi…

This is a Grafana bug → the default annotations historian generates a batch SQL insert that exceeds SQLite’s variable limit. Upgrading Grafana will not fix it. Edit /etc/grafana/grafana.ini: If you have Loki: ini [unified_alerting.state_history] enabled = true backend = loki loki_remote_url = h…

Just going back three hours I see it has happen 10 times.

hellow @scootertramp what is your evaluation interval , increased it. Reduce labels in alerts or Move Grafana DB to: Postgresql if needed

Evaluation was 30 seconds with a pending period of 30 seconds. I changed it to 10 seconds with a pending period of 20 seconds. What would moving to Postgres solve? The current Grafana db is rather small at 260M. The update frequency isn’t all that high since this is a Home Lab monitoring set-up.

Here are six messages that meet the alert settings. These are pretty consistent as they happen every hour. Also attached is my alert definition Rsyslog.json (1.2 KB) . warn <4>1 2026-05-05T08:58:51.961732-04:00 xt8-down kernel - - [meta sequenceId=“3240”] replay_ctr: warn <4>1 2026-05-05T08:58:5…

Changing interval had no effect. I tried ungrouping alert emails since the samples size seemed to match the number of warning alerts. Did not resolve error.

Just more background information. It appears this started on May 2nd. Grafana was last upgraded on Apr 18th. dpkg.log.1:2026-04-18 06:48:19 status unpacked grafana:arm64 13.0.1 dpkg.log.1:2026-04-18 06:48:19 status half-configured grafana:arm64 13.0.1 dpkg.log.1:2026-04-18 06:48:20 status instal…

Since i am using the default Grafana Contact point with the Grafana default Notification Policy and Grafana Built-in Templates. Can anybody provide any insights in to why I am getting this error for every alert that fires. error saving alert annotation batch: SQL logic error: too many SQL variable…

No change in behavior after upgrading Grafana to 13.0.2. [Screenshot 2026-06-04 065655] <30>1 2026-06-04T06:50:10.261409-04:00 raspberry05 grafana 8217 - - logger=ngalert.state.historian backend=annotations rule_uid=cf50q8nv3ooaoe org_id=1 t=2026-06-04T06:50:10.261053441-04:00 level=error msg=“Fa…

No change in behavior after upgrading Grafana to 13.1.0 [Screenshot 2026-06-23 100236] <30>1 2026-06-23T10:31:10.241667-04:00 raspberry05 grafana 42357 - - logger=ngalert.state.historian backend=annotations rule_uid=cf50q8nv3ooaoe org_id=1 t=2026-06-23T10:31:10.241336634-04:00 level=error msg=“Fa…

Thank You. I added to settings for loki and no more errors. I also run prometheus but have not added the settings for it as yet.

Error saving alert annotation batch

Grafana

scootertramp August 8, 2026, 2:50pm 13

Unfortunately moving the alert annotations out of Grafana sqllite to Loki just moved what error
I am seeing.

https://community.grafana.com/t/loki-errors-when-viewing-some-alert-rules-history/163864

Topic		Replies	Views
Database is locked Configuration	14	27657	May 1, 2024
Alert tab does not appear - Sqlite to Grafana Azure Monitor	10	1012	February 19, 2021
Control alert in grafana HA Grafana	1	370	May 11, 2021
Failed to update rule group Alerting alerting	0	445	November 6, 2023
Alert for every new row that arrives in my mysql table/dashboard Alerting alert-rule	3	3950	February 5, 2024

Error saving alert annotation batch

Related topics