IT Operations · Integration
Better Stack
Add Better Stack to your product for your customers, and give your AI agents governed access to it.
Better Stack is several products behind one brand, and the API hosts differ accordingly: uptime.betterstack.com/api/v2 serves monitors, monitor groups, heartbeats, incidents, on-call calendars and escalation policies, while log and telemetry data is queried through its own interface. Tokens are issued per team, not per user, so a customer with separate teams for staging and production needs one token per team and a single connection will silently see only part of their estate. Monitors carry check_frequency, request_timeout, expected status codes and regions, and creating one with too aggressive a frequency is the usual way customers burn through their plan allowance. Incidents are created by monitors and heartbeats rather than by you, and the useful writes are acknowledge and resolve plus posting to status pages. Heartbeats invert the model: your customer's cron job calls a URL, and the absence of a call is what raises the incident, which surprises people expecting an outbound check. fastn stores each customer's team tokens, keeps the per-team scoping straight and maintains the connection.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Better Stack account so incidents appear in your operations view
Create a monitor automatically when a customer adds a new endpoint or environment in your product
Acknowledge or resolve an incident from your own interface so responders stay in one tool
Show current on-call rota from the escalation policy next to a customer's alerts
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which monitors flapped most in the last week for one tenant and what the failure reason was
Have an agent acknowledge an active incident and record the reason, audited per tenant against that tenant's own token
Let an agent report who is on call now and when the rota next changes
Example prompt
Which of our monitors have raised incidents in the past 24 hours, and who is on call?
Set up Better Stack in 4 steps
- 01Enable the Better Stack connector from your fastn dashboard.
- 02Have each customer authorise their own Better Stack 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 Better Stack integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Better Stack integration without building it. Your customers connect their own Better Stack 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 Better Stack update is not your on-call problem.
- One integration serves your product and your agents. The same governed Better Stack 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 Better Stack, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultBetter Stack integration FAQ
How do I add a Better Stack integration to my product?
Enable the Better Stack connector in your fastn dashboard, then let each customer authenticate their own Better Stack account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Better Stack client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Better Stack account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Better Stack 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 Better Stack integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which monitors flapped most in the last week for one tenant and what the failure reason was
Who maintains the Better Stack integration?
fastn does. When Better Stack 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 Better Stack 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 Better Stack integration?
A common starting point: let a customer connect their own Better Stack account so incidents appear in your operations view. 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 Better Stack integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Better Stack does not change your per-connector cost. You can start free with 3 connected accounts.
Add Better Stack to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.