I have a requirement to monitor multiple services that start and stop at different times making alarming somewhat difficult to manage using alarm templates.
Currently for or a single service we have the following working
To manage the start and stop of an event, an external scheduled API call to dataminer runs a script to start the service using three dataminer elements and assigns the associated alarm templates to monitor the service status. At the end of the event an API call is made to stop the event and assigns the associated alarm templates that changes the status so no alarming occurs i.e. two different alarm templates per element.
This works ok for single service but for multiples services I'm not sure how to approach the monitoring. I looked at the Planned Maintenance Tool but it appears to be based on resource/parameter scheduling and I cant see how to integrate service monitoring through alarm template manipulation.
I now have 10 services all starting a stopping at different times though out the day. Any ideas on the best approach to monitor and mute the alarms. Note using manual intervention will be limited, ideally this needs to be done through automation
Hi Terry,
Would Alarm Template Groups be of use here?
You can combine this with scheduled alarm templates to have different alarm templates active on a specific service at a specific time.
If it can't be scheduled, alarm templates could still be active via conditions.
Hope this helps.