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
Possibility to monitor Zammad system health via URL from external, like gitlab is offering it. #453
Comments
Nice! |
Currently it's a system monitoring/system health check. Not monitoring of content. :-o |
I suggest open and escalted tickets ssould be available via a REST URI.. |
I think this topic is about the health state of the Zammad system. Information about the content of the system should be available via an API endpoint like @rkaldung proposed. However this is another topic so feel free to open another issue for this where we can discuss it 👍 |
Please enable HTTP Token Authentication like it's used for the API :-) |
Hi, |
Hi @jaykijay - I was just checking this topic because I too was creating a nagios check for our monitoring system. I found the checks and their output are defined in
And for the issue @monotek mentioned in #453 (comment) about reading # of open tickets, this seems to be available under the |
I would prefer a Prometheus.io metrics endpoint :D |
I'm sorry for digging through the old issues. I'd prefer not to open a new one. Might it be possible to consider the prometheus.io endpoint? The content doesn't have to be huge: metrics for "zammad_version" would be sufficient to detect if Zammad is up and responding. Of course, business metrics would be a huge plus, but that's far less important (to me/us) than the health check. |
The text was updated successfully, but these errors were encountered: