IT Operations · Integration
Datadog
Add Datadog to your product for your customers, and give your AI agents governed access to it.
Embed a Datadog integration so your customers can work their own monitors, alerts, dashboards, metrics, and logs from inside your product, with governed agent access to the same data. Alerting is latency-critical and noisy, so events arrive through triggers rather than polling and are deduplicated per incident, so a flapping check does not fill your product with identical records. fastn handles per-customer authorisation and API upkeep, so a Datadog API change is not your on-call problem.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Datadog account so alerts and monitor state appear inside your product.
Read metrics and logs per customer to show health next to the workflow your product already owns.
Create or mute a monitor from your product so operators act without switching tools.
Trigger your product the moment a monitor changes state, with duplicate alerts suppressed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads recent alerts, metrics, and logs before summarising an incident.
An agent mutes a noisy monitor or posts an event within governed permissions, with the action audited.
An agent reacts to a triggered monitor and runs the first diagnostic step.
Example prompt
Summarise the monitors that alerted in the last hour and show which services they cover.
Set up Datadog in 4 steps
- 01Open the Datadog connector from your fastn dashboard.
- 02Have each customer authenticate their own Datadog organisation with least-privilege scopes.
- 03Map the monitors, metrics, and tags your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Datadog integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Datadog integration without building it. Your customers connect their own Datadog 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 Datadog update is not your on-call problem.
- One integration serves your product and your agents. The same governed Datadog 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
AWS CloudWatch
PagerDuty
Azure MonitorOften used alongside
Tools the same teams tend to run next to Datadog, across other categories.
AppViewXDatadog integration FAQ
How do I add a Datadog integration to my product?
Enable the Datadog connector in your fastn dashboard, then let each customer authenticate their own Datadog account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Datadog client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Datadog account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Datadog 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 Datadog integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads recent alerts, metrics, and logs before summarising an incident.
Who maintains the Datadog integration?
fastn does. When Datadog 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 Datadog 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 Datadog integration?
A common starting point: connect their own Datadog account so alerts and monitor state appear inside your product. 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 Datadog integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Datadog does not change your per-connector cost. You can start free with 3 connected accounts.
Add Datadog to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.