Zammad: Possibility to monitor Zammad system health via URL from external, like gitlab is offering it.

Created on 22 Nov 2016  ·  10Comments  ·  Source: zammad/zammad

screen shot 2016-11-22 at 11 23 51

feature backlog

Most helpful comment

I would prefer a Prometheus.io metrics endpoint :D

All 10 comments

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

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 👍

@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).

Done in master.

screen shot 2016-11-23 at 15 31 42

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

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 🥇

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 https://github.com/zammad/zammad/blob/81dfe88d993793dccf9c6221af49d9a67ea5ccb0/app/controllers/monitoring_controller.rb#L39

And for the issue @monotek mentioned in https://github.com/zammad/zammad/issues/453#issuecomment-262507841 about reading # of open tickets, this seems to be available under the api/v1/monitoring/status?token=foo URI now.

I would prefer a Prometheus.io metrics endpoint :D

Was this page helpful?
0 / 5 - 0 ratings