New Relic Automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/new-relic-automation --openclawNew Relic Automation
Automate your New Relic observability workflows -- create and manage alert policies, configure notification channels (email, Slack, webhook, PagerDuty), monitor APM applications, inspect alert conditions, and integrate New Relic alerting into cross-app pipelines.
Toolkit docs: composio.dev/toolkits/new_relic
Setup
- Add the Composio MCP server to your client:
https://rube.app/mcp - Connect your New Relic account when prompted (API key authentication)
- Start using the workflows below
Core Workflows
1. List Alert Policies
Use NEW_RELIC_GET_ALERT_POLICIES to discover existing alert policies with optional filtering.
Tool: NEW_RELIC_GET_ALERT_POLICIES
Inputs:
- name: string (optional, partial match supported)
- incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET"
- page: integer (1-indexed pagination)
2. Create an Alert Policy
Use NEW_RELIC_CREATE_ALERT_POLICY to set up a new policy container for alert conditions.
Tool: NEW_RELIC_CREATE_ALERT_POLICY
Inputs:
- name: string (required) -- must be unique within the account
- incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET" (default: PER_POLICY)
Incident preferences explained:
PER_POLICY-- one issue per policy (recommended for most use cases)PER_CONDITION-- one issue per alert conditionPER_CONDITION_AND_TARGET-- one issue per condition and signal/target
3. Create Alert Notification Channels
Use NEW_RELIC_CREATE_ALERT_CHANNEL to register notification endpoints for alert delivery.
Tool: NEW_RELIC_CREATE_ALERT_CHANNEL
Inputs:
- type: "email" | "slack" | "webhook" | "pagerduty" | "opsgenie" | "victorops" (required)
- name: string (required) -- human-readable channel name
- configuration: object (required) -- varies by type:
Email: { recipients: "devops@example.com,oncall@example.com" }
Slack: { url: "<slack_webhook_url>", channel: "alerts" }
Webhook: { url: "https://hooks.example.com/alerts", auth_username, auth_password }
PagerDuty: { service_key: "<integration_key>" }
OpsGenie: { api_key, recipients, tags, teams }
VictorOps: { key: "<api_key>", route_key: "<routing_key>" }
4. Get Alert Conditions for a Policy
Use NEW_RELIC_GET_ALERT_CONDITIONS to inspect the conditions attached to a specific policy.
Tool: NEW_RELIC_GET_ALERT_CONDITIONS
Inputs:
- policy_id: integer (required)
5. Monitor Applications
Use NEW_RELIC_GET_APPLICATIONS and NEW_RELIC_GET_BROWSER_APPLICATIONS to list APM and browser-monitored apps.
Tool: NEW_RELIC_GET_APPLICATIONS
Inputs:
- name: string (optional, case-insensitive partial match)
- host: string (optional, case-insensitive partial match)
- ids: string (optional, comma-separated list of app IDs)
- page: integer (1-indexed)
Tool: NEW_RELIC_GET_BROWSER_APPLICATIONS
Inputs:
- filter[name]: string (optional, case-insensitive partial match)
- page: integer (1-indexed)
6. Manage Channels and Policies
Use NEW_RELIC_UPDATE_ALERT_CHANNEL to modify existing channels and NEW_RELIC_DELETE_ALERT_POLICY to remove policies.
Tool: NEW_RELIC_UPDATE_ALERT_CHANNEL
Inputs:
- alert_channel_id: integer (required)
- name: string (optional)
- type: string (optional, only to change type)
- configuration: object (optional, fields vary by type)
Tool: NEW_RELIC_DELETE_ALERT_POLICY
Inputs:
- policy_id: string (required) -- ID of the policy to delete
Known Pitfalls
| Pitfall | Detail |
|---|---|
| Unique policy names | NEW_RELIC_CREATE_ALERT_POLICY requires the name to be unique within the account. |
| Channel config varies by type | The configuration object for NEW_RELIC_CREATE_ALERT_CHANNEL has different required fields per channel type (e.g., recipients for email, service_key for PagerDuty). |
| Pagination required | All list endpoints return paginated results. Iterate pages until results are exhausted. |
| Policy ID type mismatch | NEW_RELIC_GET_ALERT_CONDITIONS expects policy_id as an integer, while NEW_RELIC_DELETE_ALERT_POLICY expects it as a string. |
| Channel-policy linking | After creating a channel, you must separately associate it with a policy for alerts to flow to that channel. |
Quick Reference
| Tool Slug | Description |
|---|---|
NEW_RELIC_GET_ALERT_POLICIES | List alert policies with optional filtering |
NEW_RELIC_CREATE_ALERT_POLICY | Create a new alert policy |
NEW_RELIC_DELETE_ALERT_POLICY | Delete an alert policy by ID |
NEW_RELIC_CREATE_ALERT_CHANNEL | Create a notification channel (email, Slack, webhook, etc.) |
NEW_RELIC_GET_ALERT_CHANNELS | List all configured alert channels |
NEW_RELIC_UPDATE_ALERT_CHANNEL | Update an existing alert channel |
NEW_RELIC_GET_ALERT_CONDITIONS | Get alert conditions for a policy |
NEW_RELIC_GET_APPLICATIONS | List APM applications |
NEW_RELIC_GET_BROWSER_APPLICATIONS | List browser-monitored applications |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/new-relic-automation/SKILL.mdView on GitHub Overview
New Relic Automation streamlines observability workflows by creating and managing alert policies, configuring notification channels, and monitoring APM and browser apps. It integrates with Composio MCP to embed alerting into cross-app pipelines and automate routine tasks.
How This Skill Works
Connect the Composio MCP server, authenticate with your New Relic API key, and run the built-in workflows. The skill exposes tools to list and create alert policies, register notification channels, inspect alert conditions, and monitor applications (APM and browser) with dedicated commands for retrieving policies, conditions, and applications.
When to Use It
- When standardizing and centralizing alert policies across teams and projects
- When creating a new alert policy and its associated notification channels from scratch
- When updating or deleting alert channels or policies in bulk
- When auditing current alert conditions and application coverage (APM and browser apps)
- When integrating New Relic alerting into automated CI/CD or cross-app pipelines
Quick Start
- Step 1: Add the MCP server: https://rube.app/mcp
- Step 2: Connect your New Relic account (API key authentication)
- Step 3: Start with common workflows (e.g., LIST POLICIES, CREATE POLICY, CREATE CHANNEL)
Best Practices
- Use PER_POLICY incident_preference for fewer, policy-wide issues to reduce noise
- Ensure alert policy names are unique within the New Relic account
- Register multiple notification channels (email, Slack, webhook, PagerDuty) for redundancy
- Regularly review alert conditions and their thresholds to align with SLOs
- Test workflows in a staging environment before applying to production
Example Use Cases
- Onboard a new project by creating a dedicated alert policy and linking a Slack channel and email for alerts
- Migrate from manual alert setup to automated policy creation and channel provisioning
- Consolidate APM and browser app monitoring under a single policy for consistent alerting
- Automate channel updates when incident response changes require new notification endpoints
- Audit and refresh all alert policies using LIST and GET CONDITIONS workflows to ensure alignment with current SLOs