Grafana

Nuphos authenticates to Grafana with a service account token and proxies requests to your instance, so the agent can read your dashboards, alert rules, and datasources, and explore traces.

​

Connect

​

Create a service account token

In Grafana, under Administration → Service accounts, create a service account and add a token to it. Copy the token (it’s shown once; depending on your Grafana version it may start with glsa_).

​

Connect in Nuphos

In Connectors → Connect → Grafana, enter: The connection isn’t verified at bind time, so if the token or URL is wrong it fails the first time the agent uses it — double-check both.

​

In the Nuphos app

Grafana’s alert rules feed the unified Monitoring overview — one place to see what’s configured to fire and what’s firing now, across all your observability providers, with links back to Grafana for the full detail.

​

What the agent can do for you

The agent can browse dashboards, alert rules, and datasources, and explore traces. During an incident, that means asking things like:

• “Which alerts are firing right now, and since when?”
• “Pull the latency panel for checkout over the last 6 hours and tell me when it degraded.”
• “Follow the slow trace for this request” — the agent walks the trace and correlates it with logs and deploys from your other connectors to chase the root cause.

The agent can also set up monitors and alerts for you using provider skills, proposing a plan when a change is involved.

​

Permissions & authorization

Two boundaries govern what happens through this connector:

• Hard boundary — who can use it. Only team Administrators can bind or remove the connection, and they can restrict it to specific members with a member allow-list. Within a session the agent only holds credentials you explicitly selected, re-checked on every request.
• Soft boundary — what the agent may do with it. Reading dashboards, alerts, and traces is free-form; changes go through plan approvals and Auto-authorization.

The outer limit is the service account’s role in Grafana — give it Viewer if you only want the agent reading, and Grafana enforces it regardless of what the agent is asked.

​

Good to know

• Requests are proxied through Nuphos — the agent never holds your Grafana token directly.
• You can connect several instances (prod, staging) side by side; the label keeps them distinguishable in the app and in agent sessions.