Analyze and Improve Alert Coverage

Analyze coverage gaps

Start on the Alerts Overview page, where you can check how your entities measure up to recommended standards, which entities have no condition, and which conditions are noisy or produce no signal. Act on what you find:

• To close coverage gaps, continue with the steps below.

• To quiet conditions that alert too often, refer to Reduce noise.

• To fix conditions that stopped reporting, refer to Manage conditions without signals.

  You may notice differences in the coverage numbers:

• The totals in Entities without alert conditions and Standards coverage for your entities may differ — Standards coverage counts only supported entity types: services (APM), browser applications, mobile applications, synthetic monitors, and hosts.

• The Hosts entity type doesn't show coverage percentages — because host entities are added and removed frequently.

Check standards coverage

To review coverage for every entity type, on the Alerts Overview page, click Manage standards coverage. This opens the Coverage status page.

Expand each entity type to review the condition standards New Relic recommends for it, and how many of your entities meet each standard. From here, you can do the following:

• Inspect the entities under a standard: Click Standard coverage bars, or hyperlinked entity number, and filter the list by Covered, Partially covered, or Not covered.

• Proceed to close the gaps for a standard: Click Configure if the standard isn't covered, or Manage if it's partially or fully covered. Either opens the standard's Edit conditions page.

  Tip

  Smart alerts currently don't have recommendations for entities unique to your applications or business. You can get those from Others Under Consideration and create your alert conditions manually.

Edit or create conditions

The Edit conditions page lists every condition for that standard, with each condition's threshold type, the number of entities it's active for, and its status. From here, you can do the following:

• Disable a condition: Turn off its toggle, or open it with Edit and disable it there.

• Delete a condition: Click Edit for the condition, then delete it from the condition's page.

• Adjust thresholds for an existing condition: Click Edit for the condition and use the guided flow to update its thresholds.

• Add conditions for entities that aren't covered: Select Create new alert conditions and configure the new condition.

  Legacy conditions vs. new smart alert conditions

  You can edit a legacy condition to include other entities or create a new smart alert condition for uncovered entities. New Relic recommends creating a new condition — smart alerts sets a recommended threshold per entity based on its signal history. Editing a legacy condition and adding entities applies a single threshold to all selected entities, regardless of their individual behavior.

  As smart alert conditions are entity-scoped, a new condition covers all entities matching the query — including those already covered by the legacy condition. To avoid duplicate conditions for those entities, use filters to exclude them when configuring the new condition. Refer to Configure new alert condition for details.

Configure new alert condition

The Create an alert condition page pre-scopes the condition to all entities of that standard's type. A recommended threshold is set for each entity based on its signal history. Before saving, you can do the following:

• Refine the query: Add filters to narrow the condition to a specific signal or subset of entities. Recommended thresholds update to reflect the updated query's signal history.

• Add a title: Set a name that applies to all alert events this condition generates.

• Set the issue creation preference: Choose how New Relic groups alert events from this condition into issues:

  • One issue per policy: Groups all alert events from any condition in this policy into a single issue. Use this when your policy monitors a focused scope and you want the fewest notifications.
  • One issue per condition: Creates a separate issue for each condition. All signals that breach the same condition are added to that condition's issue. Use this when you want to track incidents by condition.
  • One issue per condition and signal: Creates a separate issue for each unique condition-and-entity combination. This is the most granular option and produces the most notifications.

  Caution

  The new condition targets all entities matching the query — not only those without existing coverage. If some entities are already covered by other conditions, this results in duplicate conditions for them. To avoid duplicates, refine the query to filter out already-covered entities before saving.

  To adjust the recommended thresholds for the entities this condition covers, refer to Adjust recommended thresholds.