Connecting Grafana to Landfall

Connect your own Grafana so Beacon and every agent in the war room can query through it during an incident. That reaches every datasource your Grafana already has, including ones Landfall has no adapter for, such as Tempo.

• As a source: Beacon and joined agents list your Grafana datasources and run queries through them. It takes a base URL and a Grafana service account token with the Viewer role.
• As a trigger: a Grafana alert rule opens a war room, either through Alertmanager with a per-organization webhook secret or straight to Landfall with your organization's ingest token. See Opening a war room from a Grafana alert rule.

How it works

Beacon reads your Grafana's datasource list first, then sends a query through Grafana's own query API to the datasource that fits the incident. If you already connected Prometheus and Loki directly, querying them through Grafana adds no new reach. The value is in whatever else Grafana has configured that Landfall has no adapter of its own for. Grafana answers in its own Data Frame JSON, whatever the datasource behind it.

What you'll need

• A Grafana instance Landfall can reach. A Grafana inside your own private network is usually not reachable from a hosted Landfall the way a public SaaS API is.
• A Grafana admin who can create a service account with the Viewer role. Grafana itself enforces read-only at that role, whatever Landfall calls. A broader role works too, but Landfall never calls a write endpoint.
• An admin on your Landfall organization. Only admins can list, test and save connections.

1. Create a service account token in Grafana

1. Administration → Users and access → Service accounts

   Click Add service account, give it a name you will recognize later, such as landfall-signals, and set its role to Viewer.

2. Add service account token

   On the new service account's page, click Add service account token. Grafana shows the token once. Copy it before you close the dialog; a lost token means creating a new one.

   Grafana · Administration · Service accounts · landfall-signals

   

2. Add it to Landfall

1. Integrations → Context sources → Grafana

   Choose Integrations in the left menu, then the Grafana tile under Context sources. Enter your Grafana's base URL and the token you just created. Both fields are required.

   app.landfalls.ai · Integrations · Grafana

   

2. Test connection

   Landfall calls your Grafana's /api/datasources with the token and saves nothing. It does not use /api/health, which answers 200 even for a missing or bad token. A good answer prints Grafana reachable at https://grafana.example.com, with your own base URL.

   app.landfalls.ai · Integrations · Grafana

   

3. Save integration

   Save checks Grafana again before it stores anything. A Grafana that cannot be reached, or that rejects the token, is refused and nothing is stored. Once saved, the Grafana tile reads Configured.

   app.landfalls.ai · Integrations · Grafana

   

What it looks like

The signal catalog tells Beacon to call listDatasources first, then queryDatasource against the datasource that fits. Landfall has no shape adapter for Grafana's Data Frame answers yet, so a widget fed from Grafana is built from that raw answer.

What Beacon can read

These operations reach Beacon and every agent that joins the war room through get_signal_catalog and query_signals. See Integrations architecture.

Opening incidents from Grafana

A Grafana alert rule can open a war room by itself. Grafana either pushes the alert into the Alertmanager you already pointed at Landfall, or posts it to Landfall's own Grafana webhook. Both are on Opening a war room from a Grafana alert rule. Querying through Grafana and opening incidents from it are independent, so you can set up either one alone.

Troubleshooting

Reference