Alerts release notes

Alerts release notes

Thursday, July 30, 2020 - 16:00

Component: Muting Rules

New

We added the ability to schedule the start date/time and the end date/time for Muting Rules. Details can be found in the documents here: http://docs.newrelic.com/docs/muting-rules

Muting Rules can have one of the following statuses:

  • Active: Muting is enabled and actively being applied.
  • Scheduled: Muting is enabled but not currently active (there's a future schedule).
  • Ended: Muting is enabled, but no longer active (there's no future schedule).
  • Inactive: Muting is disabled.

The status is indicated in the Muting Rules list. In this list, you will also see

manage_muting_rules.png

This feature can be managed by both GraphQL API for Muting Rules and in the Muting Rules UI.

In the Edit Muting Rules Screen, you will see the following at the bottom of the form:

scheduler1.png

Reminder : While a muting rule is active, the violations that are opened during that period will remain muted after the muting rule period is over.

What's next? Later in the year, we will be releasing support for recurring schedules. Watch this space.

Thursday, June 4, 2020 - 10:00

Fix:

  • Fixed issue where slow web hook test notifications returned 500 timeout error message instead of actual web hook response message
Monday, June 1, 2020 - 11:00

Component : Muting Rules

New

  • The muting rules capability was released in March, 2020 with the ability to manage rules using the NerdGraph API.
  • The UI for muting rules was released to the platform on June 1, 2020. It is accessible on New Relic One, at https://one.newrelic.com, under the "Applied Intelligence" tile.

During times of planned system disruptions, a steady stream of noisy, unnecessary alerts can be a major distraction. You need to find a balance that allows you to filter out the noise yet still maintain observability and alerting on the rest of your system. With muting rules in New Relic Alerts, you can silence notifications during planned disruptions like maintenance windows, deployments, and testing.

Muting rules are available to all New Relic customers. Read more about muting rules in our documentation, at https://docs.newrelic.com/docs/muting-rules.

Friday, November 2, 2018 - 13:45

Changes

  • Notification channels created through the API now have better validation and error messaging, preventing certain types of invalid channels from making it into customer accounts.
Monday, October 22, 2018 - 10:30

New

  • Conditions now support finer grained durations.
  • Duration was a dropdown; now it is an input field.

Bug fixes

Changes

  • Max number of NRQL conditions per account raised from 2,000 to 4,000
Friday, October 5, 2018 - 06:00

Bug fixes

  • When copy-pasting queries, NRQL query errors were not displayed properly. This has been fixed and now errors are correctly shown in the NRQL condition form.
  • Fixed a cache out of sync which sometimes prevented creating labels via the API.  

Changes

  • The Violations list state layer has been re-architected to provide a snappier, more responsive UX.

Friday, September 7, 2018 - 06:00

Bug fixes

  • Fixed issue with user channels getting out of sync with user records under certain circumstances.

Changes

  • NQRL conditions now support up to 500 facets on 'Static' and 'Outlier' threshold types.

Friday, August 24, 2018 - 06:00

Bug fixes

  • The evaluation pipeline now handles 0-duration time slices, which no longer cause gaps in signals.
Friday, July 13, 2018 - 10:30

Bug fixes

  • UnknownGroup facet now ignored by condition evaluation
    • NRQL conditions containing "facet" produce an "UnknownGroup" for all unique values produced beyond a 250 limit.
    • This would cause false positives because the UnknownGroup (aggregate of all values beyond 250) was being evaluated against the condition threshold.
Monday, June 18, 2018 - 10:45

New

  • NRQL conditions now support FACETs with up to 150 values (docs)

Bug fixes

  • Entities with open violations get stuck when removed from conditions via API

Changes

  • Incident ID is now returned in violation API