Kaseya Community

Email alert generation on services starting?

This question is answered

Is there a way to setup email alerts when a particular service comes back up? We''ve got our alerts set to send out a message when a particular monitoring set service goes down but nothing to tells us that it's back up and running.

Is there a way to do this?

Thanks,
Sam

Verified Answer
  • Have you tried using Process Status in your monitoring sets.  You can add the executable that the service runs and choose the option: Alarm on transition = Up. Which from my understanding will alert you when the service starts up again.

  • Yes, so when a service stop alert is triggered execute an agent procedure that checks say after 5min if the machine is online that the service is running (if service running). If it is running then you can make the script trigger a dummy executable (runs for 30-60 sec and then closes) that can be monitored for by process monitor set which in turn generates an Alert.

    Something to consider though is when creating an Alert for a successful event this counts against your Network Health score in the Executive Summary report so a better option would be something like this.

    Have your service monitor set execute a script that checks a service or set of services are running after say 5min (use pause procedure command) after the service stop event occurred. If the Service Monitor Set could not restart the service within 5min trigger a dummy process monitor set that creates an Alert.

    You can increase the 5min period depending on the critical nature of the service and in the event of a computer restart the procedure will only execute when the agent comes back online so you won't get so may false Alerts. Also you can still log service stop events that was resolved by adding an entry in the Agent Procedure/Script log when the Procedure is executed.

All Replies
  • Have you tried using Process Status in your monitoring sets.  You can add the executable that the service runs and choose the option: Alarm on transition = Up. Which from my understanding will alert you when the service starts up again.

  • Yes, so when a service stop alert is triggered execute an agent procedure that checks say after 5min if the machine is online that the service is running (if service running). If it is running then you can make the script trigger a dummy executable (runs for 30-60 sec and then closes) that can be monitored for by process monitor set which in turn generates an Alert.

    Something to consider though is when creating an Alert for a successful event this counts against your Network Health score in the Executive Summary report so a better option would be something like this.

    Have your service monitor set execute a script that checks a service or set of services are running after say 5min (use pause procedure command) after the service stop event occurred. If the Service Monitor Set could not restart the service within 5min trigger a dummy process monitor set that creates an Alert.

    You can increase the 5min period depending on the critical nature of the service and in the event of a computer restart the procedure will only execute when the agent comes back online so you won't get so may false Alerts. Also you can still log service stop events that was resolved by adding an entry in the Agent Procedure/Script log when the Procedure is executed.

  • We used to ticket and alert on a fault and email on resumption of service.

    But what we found was all these tickets, alerts and emails created a lot of noise for us to manage.

    Our staff were swamped by the amount of info being fed to them.

    Kaseya does not have a good way of autmoatically closing tickets and alarms.

    Until it does, we will only monitor on exceptions.  

    And with over 1500 endpoints this means less noise from our RMM tool.