Can Discourse Webhooks be used for reporting uptime to a 3rd party service e.g. hund.io ?
if so, How?
3 Likes
If you just need to measure uptime, configure your tool to hit discourse.example.com/srv/status.
11 Likes
Exactly what I want! … as this is to report system uptime to someone visiting a public status page. I saw webhooks in the hund.io configuration page so I thought maybe that is something but I’ll try the Pingdom integration instead.
Thanks for help.
@pfaffman we are using Promethus Integration for advanced Stuff already … needed something to test discourse availability every few seconds and report to a 3rd party for a public status page. The solution by @Falco should work afaik but I’ll test and update how it goes.
1 Like
Well, I don’t know whether I trust it.
https://community.yellowandblack.online/srv/status says OK, but https://community.yellowandblack.online/ returns a 500 error.
2 Likes
I tried it just now and got the “Congratulations” setup page.
But if you reload a few times, you’ll stop getting that. At least, that’s my experience.
/srv/status is meant for measuring uptime only and not whether the server is returning the right response.
3 Likes
I guess that depends on how you define “uptime”…
3 Likes
In a Layman’s term, Service is Properly functioning! e.g. if there is a 500 error then it should return something other than ok!
@pfaffman I can confirm that behaviour. My system runs behind a Nginx reverse proxy and I Get okay no matter what!
Hi!
I tried to use Uptime Kuma pointing /srv/status but it tells me “Connection Refused”.
I’m using Uptime Kuma in a container, as well as Discourse. Also, for both I’m using traefik for reverse proxy. Uptime Kuma with other website works very well, but I can’t reach the Discourse app.
Can you tell me why?
Thanks in advice! 
This is a bit weird, can you share a screenshot of how you configured it? You have to set it up as keyword monitor, looking for keyword “ok” and status code 200
Hi @itsbhanusharma and thank you for the quick answer!
I set up only the status code, this is my configuration
I’m using also a docker network “proxy_network” for Traefik.
Thanks again for your help!
is uptime kuma hosted on the same machine as discourse?
EDIT:
I believe this is your problem.
Hi,
yes, the server is the same.
But with other websites works perfectly, the only problem is with Discourse.
Maybe an internal DNS resolver?
Most likely it is certificate mismatch.
And the uptime monitor will not catch issues if the server itself is down, hence it is recommended to have it on a server that’s different than the one with the rest of your application(s)
Hi, thanks for the advice.
The Discourse app has an SSL certificate generated by Traefik using Let’s Encrypt.
Right now I’m using the container check using docker socket, but it’s not reliable.
Can I try something else? I have only one server with docker.
Thanks again
change the setup to monitor ok keyword, disable ssl check.
Change the monitor type to keyword first.