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

A bound instance gets its own pages:

• Dashboards — browse and read the instance’s dashboards.
• Log explorer — query Loki with LogQL, without leaving Nuphos.
• Trace explorer — search Tempo, then walk a trace’s span tree and inspect individual spans.

Grafana’s alert rules also feed the unified Monitoring overview — one place to see what’s configured to fire and what’s firing now, across your aggregated 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. Review the target datasource, rule and notification destination before it creates or updates alerting.

​

Permissions & authorization

Team Administrators connect and remove this binding and can restrict it with a member allow-list. Select the connection for the conversation before asking the agent to use it. Provider permissions remain the outer limit, regardless of the prompt or permission mode. Individual actions follow Auto Mode and Full Access. Significant cloud infrastructure work uses plans; a ticket, repository write or routine API action does not automatically create a plan. Give explicit instructions about reviewing changes before publishing when that is the workflow you need.

​

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 agents.