08 Aug 2022
03:20 PM
- last edited on
22 Aug 2022
03:16 PM
by
Ana_Kuzmenchuk
Hi,
We are monitoring certain application services on Windows hosts, and we receive alerts when they (the services) are not running for some reason. However, we don't receive alerts when they become "unmonitored". How can this be set? Is it through "process availability" for the whole process group?
Example of the issue:
1. Service "X" is being monitored by Dynatrace
2. During Windows patching service "X" is stopped, the server is rebooted, etc.
3. After the server reboot the service doesn't come up, because it has "Manual" as startup type
4. An hour or two after that the server crashes unexpectedly and reboots itself again. Service "X" doesn't come up again (set to "Manual")
5. Since the server crash Dynatrace shows service "X" as "unmonitored" rather than "shutdown". The service started showing as running (respectively monitored) only after it was manually started on the server.
So, I guess my question is if there's a way for Dynatrace to raise a problem once a usually monitored services becomes unmonitored and how that can be achieved.
Thanks in advance!
Solved! Go to Solution.
Hi @vlazarova
there is a new feature you can find under Settings > OS service monitoring
Here you can define a rule specific to that service or e.g. in general all Manual Windows OS Services like follows:
"value": { "enabled": true, "system": "WINDOWS", "name": "Manual Windows OS Services", "monitoring": true, "alerting": true, "statusConditionWindows": "$not($eq(running))", "detectionConditionsWindows": [ { "property": "StartupType", "startupCondition": "$eq(manual)" } ], "metadata": [] }
Or in the UI it would look like this
Feel free to add more rules e.g. for a specific service only you may adda rule for its name.
Then in terms of alerting you can play around with alerting profiles if you don't want to get notified instantly in case the service takes longer to come back
Best,
Mark
Hi @mark_bley
Do you know if this option help in case if the Host is OFF, Shutdown, or the agent removed....
no, but you can trigger problems if the host is gracefully shut down
This setting is available on environment, host group or host level.
Found under Settings > Anomaly detection > Hosts