SolarWinds SAM Windows Service State is Stopping.

ballal

We have a service running in Windows that occasionally gets hung in a "stopping" state. It is not totally down, but has to be halted and restarted.   The service in question is one of a small number of services for an application. There is an application template for these services and an alert. 

For the alert trigger conditions, I see choices of Down,  and Not Running. We have The actual trigger condition set to Component - Status - is equal to - Down.

However, we are not getting alerts that the service is down. Probably because it is stuck on "stopping". Is there a better status to use such "equal to not running" or "not equal to Up"

Thanks in advance. 

mapujece

It sounds like you're dealing with a service on Windows that occasionally gets stuck in a "stopping" state, leading to issues with receiving alerts. If the current alert trigger condition is set to "Component - Status - is equal to - Down," it may not trigger alerts when the service is stuck in the "stopping" state because it's technically not considered "Down."

To address this issue, consider adjusting the alert trigger condition to "Component - Status - is equal to - Not Running" or "Component - Status - is not equal to - Up." These conditions are more likely to be detected when the service is in a non-operational state check İndir, including when it's stuck in "stopping."

By using a condition that explicitly checks for "Not Running" or the inverse of "Up," you should improve the accuracy of your alerts and receive notifications when the service encounters issues beyond just being "Down."