Skip to content
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

Closed
martini opened this issue Nov 22, 2016 · 11 comments
Assignees
Milestone

Comments

@martini
Copy link
Collaborator

martini commented Nov 22, 2016

screen shot 2016-11-22 at 11 23 51

@martini martini added this to the v1.2.0 milestone Nov 22, 2016
@martini martini self-assigned this Nov 22, 2016
@monotek
Copy link
Member

monotek commented Nov 23, 2016

Nice!
What kind of urls do you have in mind?
Also something like number of open & escalated tickets?

@martini
Copy link
Collaborator Author

martini commented Nov 23, 2016

Currently it's a system monitoring/system health check. Not monitoring of content. :-o

@rkaldung
Copy link
Contributor

I suggest open and escalted tickets ssould be available via a REST URI..

@thorsteneckel
Copy link
Contributor

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 👍

@thorsteneckel thorsteneckel changed the title Possibility to monitor Zammad via URL from external, like gitlab is offering it. Possibility to monitor Zammad system health via URL from external, like gitlab is offering it. Nov 24, 2016
@martini
Copy link
Collaborator Author

martini commented Nov 24, 2016

@rkaldung This issue is only regarding technical monitoring (like gitlab is doing it).

@rkaldung @monotek Please file a new feature issue for "content monitoring". For me the following content would be fine (1) What is the problem?, 2) How to solve it).

@martini
Copy link
Collaborator Author

martini commented Nov 24, 2016

Done in master.

screen shot 2016-11-23 at 15 31 42

@martini martini closed this as completed Nov 24, 2016
@rkaldung
Copy link
Contributor

Please enable HTTP Token Authentication like it's used for the API :-)

@jaykijay
Copy link
Contributor

Hi,
some kind of Documentation on docs.zammad.org would be nice:
It shoudl answer the Questions:
What will be shown if everthing is okay (json style)
What will be shown if something fails?
Are there some differences between something hard failing, which will stop Zammad as whole from working and something small like one E-Mail couldn't be processed?
What will then be the Output of the JSON format.
We need these Infos to build an Nagios Check to this URL and process the different States and messages.
Thank you 🥇

@mbeijen
Copy link
Contributor

mbeijen commented Apr 23, 2018

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 api/v1/monitoring/status?token=foo URI now.

@monotek
Copy link
Member

monotek commented Apr 23, 2018

I would prefer a Prometheus.io metrics endpoint :D

@antondollmaier
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants