I am working on RMM to trigger alerts when the service is stopped. Somehow I configured it but the there is an unacceptable delay on triggers. Let's say a service stops and around 15-20 minutes later (sometime more) the alerts are triggered and we are getting aware. In this situation the RMM alerts are getting useless. Any idea?
Hello Mehmet, this should not be the case. Our RMM alerts are expected to be thrown two or even more times faster, i.e. be delivered within 10 minutes or less. If you are looking for immediate reaction for alert, you can define post-action script for it. Could you please shed more light about your case? Are you trying to start service once it is stopped?
Thank you Oleg, actually 10 minutes is a bit delayed action for us. We need to catch the response of the the windows services (sql, exchange etc...) is stopped. Once stopped we need to be able to get that alert or warning within 1-2 minutes of stop. Possible?