You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Synthetic monitors |`synthetics_monitors`| Script body of SCRIPT_API and SCRIPT_BROWSER monitors |
294
+
| Legacy metric conditions |`legacy_conditions`| Monitored entity IDs (`appId`, `browserId`, `mobileId`) — fetched via REST API v2 |
295
295
296
296
#### Alert configuration health checks
297
297
298
298
| Check |`--skip` value | What is flagged | Rationale |
299
299
|---|---|---|---|
300
300
| Disabled NRQL conditions |`disabled_conditions`| Conditions with `enabled=false`| A disabled condition never fires. It should be re-enabled if monitoring is still needed, or removed to keep the policy readable. |
301
301
| Disabled synthetic monitors |`synthetics_monitors`| Monitors with `status=DISABLED` (any monitor type) | A disabled monitor produces no results and incurs no checks-per-month cost, but it clutters the monitors list and may give a false sense of coverage. |
302
-
| Legacy metric conditions |`legacy_conditions`| APM/Browser/Mobile metric conditions (non-NRQL) | These predate NRQL alerting and are no longer the recommended format. NRQL conditions offer finer control, support streaming alerts, and will receive future New Relic improvements; legacy conditions will not. |
302
+
| Legacy metric conditions |`legacy_conditions`| APM/Browser/Mobile metric conditions (non-NRQL) | These predate NRQL alerting and are no longer the recommended format. NRQL conditions offer finer control, support streaming alerts, and will receive future New Relic improvements; legacy conditions will not. Scanned via the REST API v2 (same User API key; no extra credential needed). |
303
303
| Policies with no conditions |`uncovered_alert_policies`| Alert policies that have zero conditions | An empty policy can never generate an alert. It is dead configuration that clutters the policy list and may give a false sense of coverage. |
304
304
| Policies with no notification |`uncovered_alert_policies`| Policies with at least one enabled condition but no aiWorkflow routing their alerts | When a condition fires, New Relic creates a violation and opens an issue — but if no workflow routes that issue to a destination, nobody is notified. This is one of the most common causes of silent alerting failures. |
305
305
@@ -536,12 +536,12 @@ After `apply`, your New Relic resources are under Terraform management.
0 commit comments