newrelic

What This Skill Does

The New Relic skill for OpenClaw provides a robust interface to your observability stack, allowing your AI agent to interact directly with the New Relic platform. By leveraging the New Relic GraphQL API and REST API v2, the skill enables programmatic querying of complex NRQL (New Relic Query Language) data, management of application monitoring, and retrieval of infrastructure metrics. It bridges the gap between your operational data and automated analysis, turning raw telemetry into actionable insights without requiring manual console navigation.

Installation

To integrate this skill, ensure your OpenClaw environment is properly configured. Execute the following command in your terminal: clawhub install openclaw/skills/skills/mrgoodb/newrelic

Post-installation, you must authenticate the agent by setting the following environment variables in your system profile or .env file: NEWRELIC_API_KEY (Your User or License API key) NEWRELIC_ACCOUNT_ID (Your specific New Relic account numeric identifier)

Use Cases

This skill is designed for SREs, DevOps engineers, and system administrators who require real-time observability. Use cases include:

• Automated Incident Response: Querying error rates and throughput automatically when an alert triggers.
• Performance Benchmarking: Periodically fetching application response times and comparing them against historical baselines.
• Infrastructure Auditing: Listing all active applications to ensure proper APM coverage across microservices.
• Capacity Planning: Using NRQL queries to analyze resource utilization trends over extended periods.

Example Prompts

1. "Check the current error rate for the production-api application using NRQL and tell me if it exceeds the 1% threshold."
2. "List all applications currently being monitored under my account and report their status."
3. "Analyze the last 24 hours of transaction data for the 'web-service' and identify the top three endpoints by latency."

Tips & Limitations

• Rate Limiting: Be aware that New Relic enforces rate limits on their APIs. Heavy querying may result in 429 status codes.
• Data Precision: When writing NRQL queries, ensure your time windows (e.g., SINCE 1 hour ago) are explicit to avoid unexpected aggregation results.
• Security: Always treat your NEWRELIC_API_KEY as a sensitive secret. Never hardcode it into scripts shared across public repositories.
• Permissions: Ensure the API key used has sufficient read permissions for the accounts and products (APM, Infrastructure) you intend to monitor.