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?
8 days no response? is this forum active?
[reply=“Mehmet Ali Demirci;11286”] 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?
[reply=“Oleg Sapon;11289”]
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?
[reply=“Mehmet Ali Demirci;11290”] Would you like to test a beta build that processes alerts within 1-2 minutes? Please note that sending e-mail usually adds on top of that.
[reply=“Oleg Sapon;11292”] that should be great! Let’s roll out? How?
[reply=“Mehmet Ali Demirci;11293”] Great! Allow us few days for smoke test before we provide beta build to you.
Fantastic! You should be able to see my profile or account? Right?
[reply=“Mehmet Ali Demirci;11295”] I just e-mailed you.