-
-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service Status via Labels and Bages, not being updated when service is brought down #401
Comments
I've got this working with labels, and I use
EDIT:
|
Hi! Thanks for the feedback and for your piece of code! Thank you for your feedback, I finally got it fully working! Many thanks! |
Nice that you found a solution. |
Hi,
Ever since some years ago, I have noticed that the "service monitoring" implementation, actually shows the badges/labels as "Red"/down if the ports for instance are actually closed.
Starting up a service (e.g.: FTP service on port 21), actually makes the label/badge change from red to green status, which is ok and expected. However, if I stop an FTP server listening on port 21 (e.g.: netstat correctly reports there is no port being LISTENed), but the Label/Badge does not change back to red...
Does anyone know if this is a known issue, or I am doing something wrong, somewhere?
Here's the relevant configuration that I have setup for the ftp Service monitoring:
dynamic.1.name=ftp
dynamic.1.source=netstat -nlt
dynamic.1.regexp=tcp .:(21).*LISTEN
web.status.1.content.1.line.1=Badge(data.ftp,"==21","ftp(21)","success") + Badge(data.ftp,"!=21","ftp(21)","danger")
Many thanks for any tips you might have...:)
Cheers,
Gizmo
The text was updated successfully, but these errors were encountered: