REDDIT 原始帖子
Statusmonitor for Windows services
Hi all, I am looking for a simple way to monitor if Windows Services are running. Like Uptime-Kuma (or any other Uptime service) that also shows if services like IIS are running. I hope you can help me! Thanks in advance!
Hi all, I am looking for a simple way to monitor if Windows Services are running. Like Uptime-Kuma (or any other Uptime service) that also shows if services like IIS are running. I hope you can help me! Thanks in advance!
已收录讨论
PRTG gets my vote. You can track so much more and alert on them too like if one of those services is running but not doing the thing it needs to like running SQL Agent and plopping files alert on staleness of the files.
Solarwinds, prtg, zabbix, uptime kuma, whatsup gold, logic monitor, datadog….. this list keeps going…. And going…. And goingggggg
Zabbix works for this
If you want to keep it simple? Server manager, add all servers to one 'admin' server and use it for alerts. Its far from bad but far from good.
You can use checkmk to monitor not only windows services but everything related to the systems, logs, processes, certificates, tasks, disks, cpu/ram usage, etc
CheckMK.
I use checkmk for this and it works great
Per-service via recovery tab, subsequent failure step, run a program which is a powershell script to send a teams msg or email via a direct send smart host in EXO or something like smtp2go. Or a monitoring script via task scheduler looking for service related event ids which sends an email or teams msg on fail conditions.
Another +1 for Zabbix, it also has nice integration with Grafana if you later wanted to expand and display Zabbix data in live dashboards.
If you only care whether a service is running, have you looked at PRTG or Zabbix? Both can monitor Windows services without needing a full blown RMM.
putting prometheus and grafana on the table
XorMon
Zabbix, definitely Zabbix.
A Windows service sitting at "Running" only tells you the process hasnt exited, nothing more. The one that actually pages you is the service thats still green in the SCM while the thing it does quietly stopped, so whatever tool you land on, point it at the real output (a port answering, a queue draining, a heartbeat file getting touched) rather than the service state. Ask me how I know.
What's wrong with the thing you suggested?