Monitoring phoenix channels #2635

Open
opened 2026-02-28 03:01:41 -05:00 by deekerman · 1 comment
Owner

Originally created by @Perceval62 on GitHub (Sep 27, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

So I love uptime kuma, I used it to monitor a few services and is now a Defacto install in my client's infrastructure.

I've recently gone down the Elixir/Phoenix rabbit hole...
Since uptime-kuma already supports monitoring MQTT topics, it wouldn't be too far fetched to also support Phoenix channels (based on websocket).

✔️ Solution

I don't know if you could do this with just the base feature to monitor websockets or if some implementation is needed.

Alternatives

No response

📝 Additional Context

https://hexdocs.pm/phoenix/channels.html

Originally created by @Perceval62 on GitHub (Sep 27, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description So I love uptime kuma, I used it to monitor a few services and is now a Defacto install in my client's infrastructure. I've recently gone down the Elixir/Phoenix rabbit hole... Since uptime-kuma already supports monitoring MQTT topics, it wouldn't be too far fetched to also support Phoenix channels (based on websocket). ### ✔️ Solution I don't know if you could do this with just the base feature to monitor websockets or if some implementation is needed. ### ❓ Alternatives _No response_ ### 📝 Additional Context https://hexdocs.pm/phoenix/channels.html
Author
Owner

@CommanderStorm commented on GitHub (Sep 27, 2023):

This is kind of niche/uncommon notification framework according to the developer survey.
If you/someone else would like to contribute such a monitor, here is the Contribution guide:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

If you do decide to do this, please not these two suggestions, which often push PRs back by a review-cycle:

@CommanderStorm commented on GitHub (Sep 27, 2023): This is kind of niche/uncommon notification framework according to the [developer survey](https://survey.stackoverflow.co/2023/#most-popular-technologies-webframe-prof). If you/someone else would like to contribute such a monitor, here is the Contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md If you do decide to do this, please not these two suggestions, which often push PRs back by a review-cycle: - Ensure that the PR includes screenshots of the `DOWN`/`UP` and `testing`/`cert-expiry` events. - utilisie the newer syntax used in for example https://github.com/louislam/uptime-kuma/pull/3413 or https://github.com/louislam/uptime-kuma/pull/3178/
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2635
No description provided.