I would like to suggest a way that we could change the ‘name’ of the severity that fires alerts. I am not looking at a change in the ‘functionality’ in the background or the ability to add a secondary ‘warn’ level. This is simply to acknowledge that not everything we trigger a notification on is a ‘hair on fire, all hands on deck’ critical alert. I know many of our internal processes and measures are defined by the ‘word’ assigned to severity as much as the actual issue. A critical alert by ‘rule’ is one that has significant user impact, solution outage, or broad user impact. To have a file system hit 80% and be considered ‘critical’ is a bit of overkill for our metrics.
New Relic Edit
- I want this too
- I have more info to share (reply below)
- I have a solution for this
We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.