New Relic checks
The newrelic module has 6 checks. Golden signals of New Relic APM applications and synthetic monitors, fed by the New Relic source from the entity summaries it already reads (NerdGraph entitySearch). Host golden metrics feed the Windows and Linux host checks instead.
This page is generated from the product's check catalog when the documentation is built, so the rules, intervals and default severities always match the version you are reading. Thresholds are defaults; entities and resources can override them.
| Check | Every | Default severity | Rule |
|---|---|---|---|
newrelic.apm_apdexApplication Apdex | 300s | warning | warning < 0.85 · 10m / critical < 0.7 · 5m |
newrelic.apm_error_rateApplication error rate | 300s | warning | warning > 2 percent · 10m / critical > 5 percent · 5m |
newrelic.apm_response_timeApplication response time | 300s | warning | warning > 1000 milliseconds · 10m / critical > 3000 milliseconds · 5m |
newrelic.apm_throughputApplication throughput | 300s | info | ±3σ over 7d (learning only) |
newrelic.monitor_failing_locationsSynthetic monitor failing locations | 300s | critical | warning >= 1 count / critical >= 2 count |
newrelic.monitor_success_rateSynthetic monitor success rate | 300s | warning | warning < 98 percent / critical < 90 percent |
Checks
newrelic.apm_apdex
Application Apdex
- Measures
apdex· every300s·newrelic- Rule
warning < 0.85 · 10m / critical < 0.7 · 5m· Default severity: warning- Action
- —
- Baseline
- Apdex 0.85 and above is good; below 0.7 users are frustrated. Each application's own Apdex T applies. · source
newrelic.apm_error_rate
Application error rate
- Measures
error_rate(percent) · every300s·newrelic- Rule
warning > 2 percent · 10m / critical > 5 percent · 5m· Default severity: warning- Action
- —
- Baseline
- Share of transactions with errors (New Relic reports a ratio; stored as a percentage).
newrelic.apm_response_time
Application response time
- Measures
response_ms(milliseconds) · every300s·newrelic- Rule
warning > 1000 milliseconds · 10m / critical > 3000 milliseconds · 5m· Default severity: warning- Action
- —
- Baseline
- Average across all transactions; tune per application (entity override).
newrelic.apm_throughput
Application throughput
- Measures
throughput_rpm(per_minute) · every300s·newrelic- Rule
±3σ over 7d (learning only)· Default severity: info- Action
- —
- Baseline
- Requests per minute; a sudden drop usually means traffic is not reaching the application.
newrelic.monitor_failing_locations
Synthetic monitor failing locations
- Measures
failing_locations(count) · every300s·newrelic- Rule
warning >= 1 count / critical >= 2 count· Default severity: critical- Action
- —
- Baseline
- One failing location can be the probe's network; two or more mean the endpoint is failing. · source
newrelic.monitor_success_rate
Synthetic monitor success rate
- Measures
success_rate(percent) · every300s·newrelic- Rule
warning < 98 percent / critical < 90 percent· Default severity: warning- Action
- —
- Baseline
- Share of successful checks over New Relic's summary window.
Related content
- New Relic: prerequisites and how to add resources
- Thresholds and baselines: how a default threshold is overridden