New Relic

Analytics

Neotask brings New Relic observability into plain English — OpenClaw answers your performance and reliability questions without NRQL.

What You Can Do

APM Performance Queries

Ask for transaction throughput, response times, error rates, and Apdex scores for any application or transaction name. Compare across time periods or deployment markers without writing NRQL.

Error Analysis & Fingerprinting

Retrieve the top error groups for any application, see error counts and trends, and get stack trace summaries for recurring issues — all through natural conversation.

Alert & Incident Management

List open violations, check which alert conditions are currently breaching, and get a timeline of recent incidents for a specific application or team.

Infrastructure Health

Query host CPU, memory, network I/O, and storage across your New Relic infrastructure inventory. Filter by cloud provider, region, or custom tag.

Browser & Synthetics Monitoring

Ask for page load times, Core Web Vitals, and JavaScript error rates from New Relic Browser. Check synthetic monitor success rates and failure locations.

Try Asking

  • "What's the Apdex score for our main API application this week?"
  • "Which transactions have the highest error rate in the last hour?"
  • "Are there any open alert violations right now?"
  • "Show me the top 5 error groups for the frontend app today."
  • "What's the average response time for /api/checkout in the last 24 hours?"
  • "Which of our synthetic monitors failed in the last 6 hours?"
  • "What's the memory usage trend for our production hosts this week?"
  • "Summarise the incident timeline from last night's outage."

    • Pro Tips

  • Reference applications by their exact New Relic app name for precise queries — Neotask will confirm the match before running.
  • Ask for Apdex trends over time to catch slow degradations that don't trigger threshold alerts: "how has our Apdex changed over the last 30 days?"
  • Combine APM error data with infrastructure metrics: "is the error spike on payments correlated with high CPU on the db host?" runs as one OpenClaw investigation.
  • Use deployment markers as reference points: "how did response time change after the deploy at 3pm Friday?" gives before/after context automatically.
  • Ask for error group summaries weekly — Neotask can flag new error classes that appeared this week vs. last week.

    • Works Well With