New Relic Alerts Release Notes

New Relic Alerts Release Notes

Tuesday, November 15, 2016 - 12:00

New features and functionality

Are you coming to FutureStack? If so, come see us in the New Relic Alerts booth!

Updates and changes

Bug fixes

  • Red violation regions on charts did not link to correct violation in New Relic Alerts for customers that have “Switched to New Relic Alerts”.
  • UI error when creating label-based conditions under certain circumstances.
  • NRQL stream conditions (limited release) evaluated results against a > trigger duration rather than >= trigger duration
Wednesday, October 26, 2016 - 12:00

Updates and changes

  • The policy list view is now paginated at 50 policies per page.
  • Improved performance of alerts_entity_conditions ‘add’ and ‘remove’ API endpoints where many targets are defined.
  • Improved performance of alerts_policies ‘delete’ API endpoint when policy contains more than 100 conditions.

Bug fixes

  • Regression on Open Incident view caused the auto-refresh every 60secs to break. This has been fixed.
  • Updating user preferences caused user channels to disassociate from policies in some cases. This has been fixed.
Friday, October 7, 2016 - 12:00

Notes

This first release notes post summarizes some of the recents changes for each of the sections below for the last month or so.

New features and functionality

Violations can now be searched on incidents dashboards.

20161007-alerts-release-1.png

Violation permalinks can now be found at the bottom of violation detail view.

20161007-alerts-release-2.png

Updates and changes

  • Conditions are now paginated at 100 conditions per page.
  • Violations in an incident are now paginated at 100 violations per page.
  • Incidents, policies, violations, channels, conditions and event IDs are now globally generated rather than on a per account basis. These IDs will still be in order ascending but not necessarily sequential.

Bug fixes

  • NRQL stream conditions (limited release) did not evaluate 'null' results. Now 'null' is treated as zero (0) to act similar to conditions based on metric data.
  • Fixed a bug that caused a single server with multiple disk full events occurring to be limited to one violation for the first disk full.