New Relic
When customers report issues, your AI agent checks New Relic for application health, active alerts, and performance data in real time. Incidents get acknowledged faster, root causes surface sooner, and your operations team spends less time on status update requests.
From alert policy management to application health checks, your AI agent taps into New Relic's monitoring stack to answer performance questions during active conversations.
New Relic
See how engineering teams use AI agents to surface New Relic monitoring data, manage alerts, and reduce incident response time without switching context.
An on-call engineer gets paged about a production issue and messages your AI agent for a quick status check. The agent queries New Relic's Applications API, retrieves the health status and error rate for the affected service, and summarizes the situation in seconds. The engineer gets context immediately instead of waiting for the dashboard to load, cutting initial triage time significantly.
Your SRE lead asks the agent to review all current alert policies before a quarterly infrastructure review. The AI agent pulls every policy from New Relic, groups them by incident preference, and highlights policies with no conditions attached. The team catches monitoring gaps before they become blind spots in production.
A new team joins the organization and needs alert notifications routed to their Slack channel. Instead of filing an ops ticket, the team lead tells the AI agent the channel name and type. The agent creates the alert channel in New Relic and confirms the configuration. Onboarding completes in one conversation, not one sprint.
New Relic
FAQs
The agent calls New Relic's REST API to list applications, filtering by name, host, or ID. It returns health status indicators, response times, and error rates for each monitored application. Data is fetched live from your New Relic account and never cached by Tars.
Yes. When creating an alert policy, the agent supports all three New Relic incident preference modes: PER_POLICY, PER_CONDITION, and PER_CONDITION_AND_TARGET. You can specify the preference during the conversation, and the agent sets it via the API.
Tars requires a New Relic User API Key (not an Ingest or Browser key). Generate one from your New Relic account under API Keys in the account settings. You also need to specify your account region (US or EU) to route API calls correctly.
No. Tars queries New Relic's API in real time during conversations. Application metrics, alert policies, and channel configurations are fetched on demand and used only to generate responses. No monitoring data is persisted outside of your New Relic account.
The agent can delete alert policies by policy ID. You can configure approval rules in Tars so destructive actions like policy deletion require confirmation or manager approval before execution. This prevents accidental removals during conversations.
New Relic AI (NRAI) works inside the New Relic dashboard for query generation. Tars brings New Relic data into your existing communication channels like Slack, WhatsApp, or your website. Your team gets observability answers where they already work, without switching tools.
Yes. The agent supports creating and updating alert channels of any type supported by New Relic, including email, Slack, PagerDuty, and custom webhooks. You specify the channel type and configuration details, and the agent handles the API call.
The agent handles this gracefully. If a name or ID query returns no results from New Relic, it informs the user that no matching application was found and suggests checking the application name or verifying that the service is instrumented with a New Relic agent.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.
Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.
Email - sales@hellotars.com
.png)
%201.png)
%201.png)
