# Webhook for Discourse Uptime Monitoring?
**URL:** https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830
**Category:** Development
**Created:** [December 11, 2017, 3:43pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830 "2017-12-11T15:43:18Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [December 11, 2017, 3:43pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/1 "2017-12-11T15:43:18Z")
Can Discourse Webhooks be used for reporting uptime to a 3rd party service e.g. [hund.io](http://hund.io) ?
if so, How?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 11, 2017, 3:46pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/2 "2017-12-11T15:46:30Z")
See [Discourse Prometheus](https://meta.discourse.org/t/prometheus-exporter-plugin-for-discourse/72666) and [Discourse Stats | Grafana Labs](https://grafana.com/dashboards/3539).
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 11, 2017, 3:47pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/3 "2017-12-11T15:47:23Z")
> [@itsbhanusharma](#):
>
> reporting uptime
If you just need to measure uptime, configure your tool to hit `discourse.example.com/srv/status`.
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [December 11, 2017, 3:48pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/4 "2017-12-11T15:48:57Z")
> [@Falco](#):
>
> If you just need to measure uptime, configure your tool to hit [discourse.example.com/srv/status](http://discourse.example.com/srv/status).
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](http://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.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 12, 2017, 12:31am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/6 "2017-12-12T00:31:47Z")
Well, I don’t know whether I trust it.
[https://community.yellowandblack.online/srv/status](https://community.yellowandblack.online/srv/status) says OK, but [https://community.yellowandblack.online/](https://community.yellowandblack.online/) returns a 500 error.
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [December 12, 2017, 12:36am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/7 "2017-12-12T00:36:14Z")
> [@pfaffman](#):
>
> returns a 500 error
I tried it just now and got the “Congratulations” setup page.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 12, 2017, 12:37am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/8 "2017-12-12T00:37:12Z")
But if you reload a few times, you’ll stop getting that. At least, that’s my experience.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [December 12, 2017, 12:37am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/9 "2017-12-12T00:37:42Z")
`/srv/status` is meant for measuring uptime only and not whether the server is returning the right response.
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [December 12, 2017, 12:57am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/10 "2017-12-12T00:57:41Z")
I guess that depends on how you define “uptime”…
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [December 12, 2017, 1:43pm UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/11 "2017-12-12T13:43:00Z")
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!
---
### Author:  [@FrancescoM](https://meta.discourse.org/u/FrancescoM)
#### Post date: [January 16, 2026, 9:31am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/13 "2026-01-16T09:31:28Z")
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! 🙂
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 16, 2026, 9:36am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/14 "2026-01-16T09:36:12Z")
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
---
### Author:  [@FrancescoM](https://meta.discourse.org/u/FrancescoM)
#### Post date: [January 16, 2026, 9:58am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/15 "2026-01-16T09:58:34Z")
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!
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 16, 2026, 10:01am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/16 "2026-01-16T10:01:17Z")
is uptime kuma hosted on the same machine as discourse?
EDIT:
> [@FrancescoM](#):
>
> I’m using also a docker network “proxy\_network” for Traefik.
I believe this is your problem.
---
### Author:  [@FrancescoM](https://meta.discourse.org/u/FrancescoM)
#### Post date: [January 16, 2026, 10:54am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/17 "2026-01-16T10:54:18Z")
Hi,
yes, the server is the same.
But with other websites works perfectly, the only problem is with Discourse.
Maybe an internal DNS resolver?
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 16, 2026, 10:55am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/18 "2026-01-16T10:55:48Z")
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)
---
### Author:  [@FrancescoM](https://meta.discourse.org/u/FrancescoM)
#### Post date: [January 16, 2026, 11:04am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/19 "2026-01-16T11:04:34Z")
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
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 16, 2026, 11:06am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/20 "2026-01-16T11:06:42Z")
> [@FrancescoM](#):
>
> Can I try something else?
change the setup to monitor ok keyword, disable ssl check.
---
### Author:  [@FrancescoM](https://meta.discourse.org/u/FrancescoM)
#### Post date: [January 16, 2026, 11:22am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/21 "2026-01-16T11:22:14Z")
> [@itsbhanusharma](#):
>
> change the setup to monitor ok keyword
Ok,
I removed the SSL check, but how can I set the “ok” keyword? Here?
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 16, 2026, 11:26am UTC](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830/22 "2026-01-16T11:26:40Z")
Change the monitor type to keyword first.
[Next page](https://meta.discourse.org/t/webhook-for-discourse-uptime-monitoring/75830.md?page=2)