Alerts Release Notes

Alerts Release Notes

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