Gleap AI agents can use New Relic through Composio, for teams that observe their applications in New Relic and collect customer bug reports in Gleap. Kai Code, Kai Support and custom agents can query errors and transactions with NRQL and check which deployment went out before customers started reporting a problem.
What a Gleap agent can do in New Relic
- Errors behind a report: Query Error runs an NRQL query for errors in the service and time window of a Gleap bug report.
- Any metric you can query: Execute NRQL Query reads transactions, response times or custom events, for example the error rate of the checkout service over the last hour.
- What changed recently: List Deployments shows the deployments of an application, so the agent can point out a release that lines up with the first customer report.
- The right service: Search Entities finds the application or service by name, so queries target the right entity.
- Evidence while fixing: with New Relic in Kai Code’s MCP settings, Kai Code can run the same queries while it prepares a pull request for your engineers to review.
Example: errors after a Tuesday release
On Tuesday afternoon, several customers report through the Gleap widget that saving their profile fails. Kai Support investigates the ticket, runs an NRQL query in New Relic and finds a spike of validation errors in the profile service that starts minutes after a deployment. It notes the deployment and the error message in its findings and prepares a coding task. A teammate decides whether to roll back or start the fix.
How to connect New Relic
- In Gleap, open Kai Code, click Settings and open MCP.
- Click Add MCP server, search for “New Relic” and select it.
- Enter your New Relic API key and any other details the form asks for, then click Connect New Relic.
- Open the New Relic server and switch off the tools Kai Code should not call, such as Delete Entity, the alert condition changes and the golden metric overrides.
- For a custom agent, add New Relic under the agent’s Tools with Add tool instead, then publish and test it.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with New Relic?
Yes. Kai Code, Kai Support and custom agents use New Relic through Composio’s New Relic toolkit, authenticated with a New Relic API key. They query New Relic while they run; Gleap does not store your telemetry.
What can a Gleap AI agent do in New Relic?
It can run NRQL and NerdGraph queries, search entities, read dashboards, deployments and alert conditions, create deployment markers and change alert conditions, tags and entity settings. Alert changes affect your on-call team, so leave those tools off.
Which Gleap plan includes the New Relic integration?
Kai Code and Kai Support’s investigations can use New Relic on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use New Relic are part of the Team, Pro and Enterprise plans. The New Relic user behind the API key decides which accounts the agents can query. AI usage is billed separately; see pricing.
Can the agent record a deployment marker?
Yes. Create Deployment Marker records a deployment in New Relic, which can help if a teammate wants the timing of a hotfix on the charts. If your CI pipeline already creates markers, the agent only needs to read them.
