action #26842
closed[tools] Provide machine-readable version of openqa worker status
0%
Description
https://openqa.opensuse.org/admin/workers
is currently not available in a machine-readable format (json, yaml, whatever)
This makes admins and monitoring people really sad.
By contents of this directory: https://github.com/os-autoinst/openQA/tree/53ab930447660c74df5965db5131f255bdf54b5c/templates/admin/workers
it should be really easy for a dev - who is familiar with the openQA internals - to add another template there^ which is yaml or json - and not HTML
a simple "Worker name" - "Status" would be suitable for an "easy monitoring"
Please add a documentation, which status are possible + what are there meanings as well, as i found it now only in the code and even there it was not really well explained in the worker_status template file.
Thanks a lot.
Side note: came up after power outage of Nuremberg openQA, that there is no proper monitoring of all the workers
Regarding ticket in openSUSE-Admin Queue: https://progress.opensuse.org/issues/26840
Updated by coolo over 6 years ago
- Subject changed from Provide machine-readable version of openqa worker status to [tools] Provide machine-readable version of openqa worker status
- Priority changed from Normal to High
Updated by coolo over 6 years ago
It's https://openqa.suse.de/admin/workers.json actually
Updated by okurz over 6 years ago
- Status changed from New to In Progress
- Assignee set to okurz
And if you don't like that then try http://openqa.suse.de/api/v1/workers.
Each entry contains
- the hostname, not the complete dns entry so a suffix e.g. ".qa" or ".arch" might be missing.
- the boolean flag "connected" which can be 0 or 1 depending on the connection to the websockets server on openqa.suse.de
- the field "status" which can be "dead", "idle", "running".
A worker can be considered "up" when "connected=1" and "status!=dead"
I will try to improve the documentation
Updated by okurz over 6 years ago
Updated by okurz over 6 years ago
- Status changed from In Progress to Resolved
PR for documentation still open, new API route active already.