Route Grafana alerts to owner threads
Connect
SPIRITT
GrafanaGrafana signals
Operational follow-through
SPIRITT turns public dashboard panel metrics and backend status into investigations, owner handoffs, and custom reliability tools. It can also send OTLP logs to Loki to make your own workflows observable.
What you can do with Grafana.
Separate failure signals
Distinguish Grafana server and database health from public panel results and backend ring status before routing an incident.
Carry evidence into action
Give responders timestamped panel data, replica leadership changes, and ring observations alongside an accountable work item.
Instrument your workflows
Build custom operations tools and send their execution logs to Loki using OTLP, with sensitive fields excluded before transmission.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for observability checks, incident coordination, or a custom reliability tool.
02
Connect Grafana
Connect Grafana with a bearer token and access appropriate to your mission's public panels, health checks, or backend operations.
03
Delegate an outcome
Specify the panels, services, thresholds, and owners. SPIRITT builds the workflow, gathers evidence, and carries follow-up into connected tools.
Hand over a mission.
Choose a mission. Make it yours.
Put Grafana to work.
Put your reliability signals to work
Questions
Grafana, with SPIRITT.
01Which Grafana signals can SPIRITT work with?+
SPIRITT can query public dashboard panels, check Grafana server and database health, inspect distributor HA leadership, and retrieve selected Loki and Mimir ring status. It can also list store gateway tenants, check Enterprise license status, retrieve public signing keys, and submit OTLP logs to Loki.
02What access does this connection need?+
The connection uses a bearer token. Scope access to the checks or log submissions your mission requires. Grafana health, Loki ring status, and Mimir ring status concern different components, so your environment must expose the relevant operations. A successful Grafana health check does not establish that every backend is healthy.
03Can SPIRITT query private dashboards or edit Grafana alerts?+
This connection queries panels on public dashboards. It does not support private dashboard queries, dashboard editing, alert-rule changes, or general log and trace searches. SPIRITT can run an external checking workflow around public panel data and component status without changing Grafana's native alert configuration.
04How can checks become a recurring incident workflow?+
SPIRITT can schedule supported checks, store observations, apply your thresholds, and coordinate incident threads in Slack and work items in Linear or Jira. Public panel data supplies metric evidence while ring and health checks add component context. Recovery updates follow the same incident record instead of creating a new alert for every sample.
05What useful tools can SPIRITT build around Grafana?+
SPIRITT can build a maintenance acceptance app that checks observed ruler ring membership against your target, an OTLP payload workbench with redaction tests, or a release comparison tool using public latency, error, and traffic panels. These are custom tools around Grafana data and log submission, not newly created native Grafana dashboards.
06Is submitting OTLP logs the same as searching Loki?+
No. OTLP log submission sends events into Loki; it does not retrieve them or prove they are visible in a downstream query. SPIRITT can prepare payloads, redact sensitive fields, submit events, and record submission outcomes. This connection supports log submission, not searches of stored logs.