IT Operations · Integration
New Relic
Add New Relic to your product for your customers, and give your AI agents governed access to it.
Embed a New Relic integration so your product can act on the telemetry a customer's systems already produce instead of asking them to export it. New Relic holds entities, alert conditions, incidents, dashboards and the metric, event, log and trace data your users query with NRQL, so a product feature can show the state of a service rather than a link to another tool. Alerts arrive through event triggers rather than polling, and events are deduplicated per incident, which matters because a flapping condition should not create a queue of identical records. Each customer connects their own account, so queries and reads are scoped to their tenant and audited. fastn owns the credentials, retries, rate limits and API upkeep, and the same connection serves your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own New Relic account so their service health and alerts surface inside your product with no per-customer code.
React to a New Relic incident with an event trigger so your product opens, routes or escalates the right record while the condition is live.
Run a scoped NRQL query when a user is investigating and show the result in the context they are already working in.
Support each customer's own entities, alert conditions and dashboards as configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent investigates an incident by querying that customer's own telemetry within scoped permissions.
An agent correlates an alert with the deployment and traces around it and explains what it found, with every read audited.
An agent reports which incidents fired for one tenant overnight and which are still open.
Example prompt
Query New Relic for errors on this service in the last hour and tell me what changed before they started.
Set up New Relic in 4 steps
- 01Enable the New Relic connector in your fastn dashboard.
- 02Have each customer supply an API key for their own account so queries run under their access.
- 03Map the entities, queries and alert conditions your product needs, then enable the triggers you want.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the New Relic integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a New Relic integration without building it. Your customers connect their own New Relic 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 New Relic update is not your on-call problem.
- One integration serves your product and your agents. The same governed New Relic 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
Datadog
Dynatrace
PagerDutyOften used alongside
Tools the same teams tend to run next to New Relic, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultNew Relic integration FAQ
How do I add a New Relic integration to my product?
Enable the New Relic connector in your fastn dashboard, then let each customer authenticate their own New Relic account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no New Relic client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own New Relic account?
Yes. Every connection is scoped to the individual customer, so each authorises their own New Relic 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 New Relic 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 investigates an incident by querying that customer's own telemetry within scoped permissions.
Who maintains the New Relic integration?
fastn does. When New Relic 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 New Relic 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 New Relic integration?
A common starting point: let each customer connect their own New Relic account so their service health and alerts surface inside your product with no per-customer code. 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 New Relic integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding New Relic does not change your per-connector cost. You can start free with 3 connected accounts.
Add New Relic to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.