IT Operations · Integration
Log Insight
Add Log Insight to your product for your customers, and give your AI agents governed access to it.
Embed a Log Insight integration so your product can query the log data a customer's infrastructure already produces instead of asking them to export it. Each customer connects their own environment, so queries and alert reads run under their credentials and stay scoped to their tenant. Alerts arrive through event triggers rather than polling, and events are deduplicated per condition, which matters because a flapping check should not create a queue of identical records for your users. fastn owns the auth, retries, rate limits and API upkeep, and the same governed connection is what your AI agents use when they investigate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Log Insight environment so your product can query their log data in place.
React to a Log Insight alert with an event trigger so your product opens the right record while the condition is still live.
Run a scoped log query from inside your product when a user is investigating, and show the result in context.
Support each customer's own log sources and alert definitions 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 the customer's own log data within scoped permissions.
An agent correlates an alert with the log lines around it and explains what it found, with each read audited.
An agent summarises which alerts fired for one tenant overnight and which are still unresolved.
Example prompt
Query Log Insight for errors on this service in the last hour and tell me what changed.
Set up Log Insight in 4 steps
- 01Enable the Log Insight connector in your fastn dashboard.
- 02Have each customer connect their own environment so queries run under their credentials.
- 03Map the queries and alerts your product needs, then enable the triggers you want to react to.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Log Insight integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Log Insight integration without building it. Your customers connect their own Log Insight 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 Log Insight update is not your on-call problem.
- One integration serves your product and your agents. The same governed Log Insight 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
Azure MonitorOften used alongside
Tools the same teams tend to run next to Log Insight, across other categories.
AWS Secrets Manager
AppViewXLog Insight integration FAQ
How do I add a Log Insight integration to my product?
Enable the Log Insight connector in your fastn dashboard, then let each customer authenticate their own Log Insight account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Log Insight client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Log Insight account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Log Insight 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 Log Insight 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 the customer's own log data within scoped permissions.
Who maintains the Log Insight integration?
fastn does. When Log Insight 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 Log Insight 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 Log Insight integration?
A common starting point: connect their own Log Insight environment so your product can query their log data in place. 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 Log Insight integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Log Insight does not change your per-connector cost. You can start free with 3 connected accounts.
Add Log Insight to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.