Christian Boltz wrote:
Am Donnerstag, 23. August 2018, 09:58:38 CEST schrieb Ludwig Nussel:
Looking at the upstream cachet documentation
there seems to be api
support to automate updating the status of services. What needs to be
done to get a token there and hook up services?
I have to admit that I never played with the API, so I can only give you
A good starting point is having an account on status.o.o. I took your
mail as a request for that ;-) and just sent you an invitation.
Thanks! I tested cachet-url-monitor with software.opensuse.org
Unfortunately caused some spam as I didn't notice it was too aggressive
changing status and even creating incidents :-( Sorry for that!
So maybe that is a way to get status.o.o to warn interested parties in
time if something bad happens.
The config I use for software.o.o is this one:
- type: HTTP_STATUS
- type: LATENCY
- type: REGEX
Obviously the service would need to run somehwere else than my
workstation to be useful. I've switched the test run off now to avoid
further havoc :-)
Anyways, the monitor is basically working. I made a package here:
Feel free to take if it's useful.
PS: Looks like Cachet is packaged in Lars' home. I guess the canonical
location for something that is deployed on openSUSE infrastructure
should be somewhere else :-)
(o_ Ludwig Nussel
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
To unsubscribe, e-mail: heroes+unsubscribe(a)opensuse.org
To contact the owner, e-mail: heroes+owner(a)opensuse.org