Alert Tuning - Automatically include the datasource-defined threshold when adding custom threshold


Recommended Posts

I have an app admin who wants to suppress CPU critical alerting from 10PM to 4AM for his servers---ok, not a problem. We created a dynamic group filtering for his servers and set a custom alert threshold for the desired time without a critical threshold. The issue I'm having is for the rest of the day from 4:01 AM to 9:59 PM. This app admin does not have a good use case to suppress alerting during these hours, so the standards from the datasource should apply. But in order to get those standard alert thresholds take effect, I am finding I have to create another manual effective threshold for the remaining hours.

This becomes a problem if we ever have to change the datasource-defined alert threshold. Having the datasource-defined global threshold automatically included (and linked/updated) as the lowest layer of the Effective Threshold stack would alleviate the need to track and update all of the one offs when new standards are approved.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.