Skip to main content
Connect your Grafana instance so Myrmex can check its health, inspect dashboards, and read metrics. Myrmex reaches Grafana over its HTTP API through a Collector on your network. Every request runs live, on demand — Myrmex returns only what you ask for and copies or stores nothing from Grafana on its side. Credentials are resolved on your side and never pass through the model.

​
What Myrmex Can Do

Check health

Read Grafana’s health and status to confirm the instance is up.

Inspect dashboards

List and inspect dashboards live to see what is being monitored.

Read metrics

Pull metrics through the API on demand and return only what you asked for.

Review data sources

List configured data sources to understand where the data comes from.

​
Before You Start

  • A Collector that can reach Grafana over HTTP or HTTPS (default port 3000). See Collector mode.
  • A service account (or API key) with at least the Viewer role.

​
Step 1 — Create the Credential in Grafana

1

Create a service account

In Grafana, go to Administration → Users and access → Service accounts and add a service account with the Viewer role — enough for health, dashboards, and metrics.
2

Add a token

On the service account, click Add service account token, set an optional expiry, and copy the token. Myrmex sends it as a Bearer token.
Use a service account with the Viewer role for read-only monitoring. Grant a higher role only if you later need Myrmex to change Grafana.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Grafana, then fill in:

​
Connect

Click Connect to validate the API connection and finish. Grafana then appears under Environment → Integrations, and you can ask about it in the Workspace or through the Integration Specialist agent.
Behind a reverse proxy, Grafana may serve on 443 under a sub-path. Point the URL and Port at the address the Collector can actually reach.