---
name: New Relic Automation
description: "สกิลสำหรับ Automation ของ New Relic ผ่าน Rube MCP (Composio) ใช้เมื่อต้องค้นหา schema ล่าสุด ตรวจสอบเครื่องมือ และดำเนินงานอัตโนมัติที่เกี่ยวข้องกับงาน AI, Agent, Machine Learning, LLM, RAG, Prompt, Automation และงานวิจัย AI"
requires:
  mcp:
    - rube
---

# สกิล: New 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](https://composio.dev/toolkits/new_relic)

---

## Setup

1. Add the Composio MCP server to your client: `https://rube.app/mcp`
2. Connect your New Relic account when prompted (API key authentication)
3. 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 condition
- `PER_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](https://composio.dev)*
