$ loading_
自动化管理 New Relic 告警、通知与应用监控流程，提升运维观测效率。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "New Relic Automation" 技能： 1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/new-relic-automation/SKILL.md 2. 保存为 ~/.claude/skills/new-relic-automation/SKILL.md 3. 装好后重载技能，告诉我可以用了
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://rube.app/mcpUse 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)
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/targetUse 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: "[email protected],[email protected]" }
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>" }
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)
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)
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
| 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). |
…
帮助用户用自然语言查询并管理 New Relic 监控、告警与性能数据。