IT Operations · Integration
Grafana
Add Grafana to your product for your customers, and give your AI agents governed access to it.
Grafana has two distinct APIs and implementers regularly aim at the wrong one: grafana.com/api is the Cloud account API for stacks, orgs and access policies, while dashboards, folders, alert rules, datasources and annotations live on the stack itself at https://{stack}.grafana.net/api, each needing its own token. Stack tokens are service account tokens with role scopes, and the older API keys are being retired, so a connection created against a legacy key can stop working without the endpoint changing. Dashboards are addressed by uid, are versioned on every save, and are read-only through the API when they were provisioned from files, which returns a permission error rather than an obvious explanation. Unified alerting splits rules, contact points and notification policies into separate provisioning endpoints, and rules provisioned from disk are likewise locked. Grafana OnCall and Grafana Incident are separate services with their own base paths and tokens, so on-call schedules are not reachable from the core stack API. fastn holds each customer's stack host and token, keeps the scopes attached to that tenant, and manages rotation.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Grafana stack so your product can read the dashboards and alert rules they already run.
Write annotations into their Grafana when a deployment or incident happens in your product, so graphs carry the context.
Mirror firing alerts into your own incident view without asking the customer to rebuild notification policies.
Create a folder and a starter dashboard in the customer's stack when they onboard, using their own datasources.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent list which alert rules are currently firing and which folder owns them, audited per tenant.
Let an agent read a dashboard's panels and explain what a spike is being measured against, with write access withheld.
Allow an agent to add an annotation marking a change window, with the token scope limited to that tenant.
Example prompt
Which Grafana alert rules have been firing for more than an hour, and what dashboards do they point to?
Set up Grafana in 4 steps
- 01Enable the Grafana connector from your fastn dashboard.
- 02Have each customer authorise their own Grafana account, so calls run under their credentials rather than a shared key.
- 03Decide which incidents, alerts and on-call schedules your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Grafana integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Grafana integration without building it. Your customers connect their own Grafana account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Grafana update is not your on-call problem.
- One integration serves your product and your agents. The same governed Grafana connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
ServiceNow
Datadog
PagerDutyOften used alongside
Tools the same teams tend to run next to Grafana, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultGrafana integration FAQ
How do I add a Grafana integration to my product?
Enable the Grafana connector in your fastn dashboard, then let each customer authenticate their own Grafana account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Grafana client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Grafana account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Grafana account and only ever sees their own incidents, alerts and on-call schedules. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Grafana integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent list which alert rules are currently firing and which folder owns them, audited per tenant.
Who maintains the Grafana integration?
fastn does. When Grafana changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How fast does a Grafana alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the Grafana integration?
A common starting point: let a customer connect their own Grafana stack so your product can read the dashboards and alert rules they already run. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Grafana integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Grafana does not change your per-connector cost. You can start free with 3 connected accounts.
Add Grafana to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.