Quantcast
Channel: THWACK: All Content - Server & Application Monitor
Viewing all articles
Browse latest Browse all 12281

Can you pull component details from a template for alerting in SAM?

$
0
0

Let's say I have a Template called Server Monitors. In that template I have a number of components, including some disparate ones. For example say I have the following components:

 

  • My_Main_Service
  • My_Other_Service
  • Some_Important_Service
  • Number_Of_IIS_Users_on
  • Event_Log_3456
  • Msgs_In_All_MessageQueues

 

Right now we have built alerts on such a template that fires and says there's a problem with one of the things inside this template. But I haven't been able to figure out how to provide specifics without writing a separate alert for every single component in this template. In other words, I have to write 6 alerts on this template if I want something that isn't ambiguous. One for My_Main_Service is down, one for Event_Log_3456 found, and another for Msgs_In_All_MessageQueues exceeding threshold, and so on.

 

Is there a way to write a single alert, that fires when anything in this template exceeds any threshold, but only provide details on the item that's having the problem?

 

For example... let's say My_Main_Service goes down, I would like to have an alert that say "Server Monitors" template fired with a message that just that one service is down without having to list all the items in the template and their current state so that you have to read through them.

 

Even better, fire on the template, then provide details for the item. Like if item Event_Log_3456 fires, the message contains the output of the event log, and if the Msgs_In_All_MessageQueues fired, the message would contain the number of messages in the queue, etc. You probably get the idea of what I'm asking here.

 

Having the same problem with the Groups alerts. I send a message when the Group is having a problem, but not finding a way to describe what that problem in the e-mail about why that group is alerting. I'm sure I'm missing something here. So many variables to go through and many don't seem to work as expected.


Viewing all articles
Browse latest Browse all 12281

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>