ceven

New Relic

Connects your observability data to your incident response workflows, automatically creates alert policies when new services deploy, and syncs application health metrics to your ticketing system.

Try New Relic in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native New Relic integration

    • Describe the outcome and Ceven picks the right New Relic calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your New Relic data, across all 158 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke New Relic access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in New Relic, when, and on whose behalf.
    • The agent pauses and asks when New Relic is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach New Relic.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every New Relic action to support review and sign off.

Supported tools

Every action Ceven's agents can run on New Relic, and when to use it.

Create Alert Notification Channel
Use this when you need to register a new endpoint such as email or webhook for alert notifications.
Create Alert Policy
Use this when you need to programmatically set up a new alert policy to monitor specific system metrics.
Delete alert policy
Remove an existing alert policy using the policy id. Use this after confirming the policy is no longer needed.
Get Alert Channels
Pull a list of all configured alert notification channels to verify where alerts are being sent.
Get Alert Conditions
Retrieve the specific conditions and thresholds for a specified policy using the policy id.
Get Alert Policies
Pull a list of existing alert policies with optional filtering and pagination for auditing.
Get Applications
List all monitored applications or filter by name and host to check connectivity status.
Get Browser Applications
Retrieve all browser applications to monitor front end performance and user experience.
Update Alert Notification Channel
Modify the settings of an existing notification channel after verifying the channel id.
Create Alert Condition
Define a new threshold for a metric that should trigger an alert within a specific policy.
List NRQL Queries
Pull a list of saved queries to identify which metrics are most frequently monitored.
Pause Alert Policy
Temporarily stop notifications for a specific policy during planned maintenance windows.

12 actions · scroll to see them all

Frequently asked questions

Ceven uses New Relic User API keys for authentication. When you connect your account, you provide the API key associated with a user who has the necessary permissions to read and write policies and channels. We store this key using AES 256 encryption at rest and only inject it into the request header when the agent performs an action on your behalf. This ensures that your credentials are never exposed in plain text within the workflow logs or to the underlying language model. You can rotate your New Relic API key at any time in the New Relic account settings, which will require a quick update in the Ceven integration panel to restore connectivity.
Yes. New Relic enforces strict rate limits on their REST API, particularly for write operations like creating alert policies or updating notification channels. If a Ceven workflow attempts to create hundreds of policies in a tight loop, New Relic will return a 429 too many requests error. Ceven handles this by implementing an exponential backoff strategy, meaning the agent will wait and retry the request automatically. However, for very large scale migrations, we recommend batching your requests. Be aware that New Relic API limits are often tied to your specific account tier, so higher tier plans generally have more breathing room for automated agent activity.
Ceven can create alert conditions based on NRQL queries if you provide the query string. The agent can help you draft the query based on the metrics you want to track, such as average response time over five minutes. Once the query is validated, Ceven uses the New Relic API to bind that query to a specific alert policy. It can also set the critical and warning thresholds. If you are unsure of the exact attribute names in your data, you can ask the agent to list your existing applications first to identify the correct naming conventions before it attempts to write the new alert condition.
Yes. Ceven has separate actions to retrieve and manage both server side application performance monitoring and browser based monitoring. This allows you to build workflows that correlate back end latency with front end user experience. For example, you can create a workflow that triggers when a browser application reports a spike in JavaScript errors and then automatically checks the health of the corresponding back end APM service. This cross stack visibility is essential for debugging distributed systems where a failure in a microservice manifests as a generic error page for the end user.
Absolutely. Ceven can create and update notification channels for various endpoints including email, Slack, PagerDuty, and custom webhooks. You can build a workflow that maps specific alert policies to different teams. For instance, database alerts can be routed to the DBA team webhook while front end alerts go to the UX team Slack channel. The agent manages the mapping by first creating the notification channel and then associating that channel ID with the relevant alert policy. This eliminates the need for a manual administrator to set up routing for every new service that gets deployed to the cloud.
If a policy is deleted in the New Relic UI, Ceven will encounter a 404 not found error the next time it tries to read or update that specific policy ID. The agent is designed to handle these errors gracefully by notifying the workflow owner that the resource no longer exists. You can set up a synchronization workflow that periodically lists all active policies in New Relic and compares them against your internal service registry. If the agent finds a discrepancy, it can either alert you or automatically recreate the missing policy based on a saved template.
While Ceven cannot change your billing plan, it can help you identify waste. You can build a workflow that lists all alert policies and identifies those that have not triggered an event in the last ninety days. The agent can then present a list of these dormant policies and ask for your permission to delete them. This keeps your monitoring environment clean and prevents alert fatigue. Additionally, the agent can track the number of ingested entities and notify you when you are approaching the limits of your current data ingestion tier, allowing you to adjust your sampling rates before you incur overage charges.
No. Ceven does not store your telemetry, logs, or metric data. It acts as a control plane that sends commands to New Relic and receives responses. When the agent pulls a list of applications or alert conditions, that data exists only in the short term memory of the current workflow execution to allow the agent to make decisions. Once the workflow finishes, the data is cleared. Your actual observability data remains securely inside New Relic. Ceven only handles the metadata required to manage your monitoring configuration and the specific event data needed to trigger an automated response.

Alternatives to New Relic

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Datadog logoDatadogDynatrace logoDynatraceSplunk logoSplunkGrafana logoGrafana

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect New Relic and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free