mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Monitoring phoenix channels #2635
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2635
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Perceval62 on GitHub (Sep 27, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ 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
@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:
DOWN/UPandtesting/cert-expiryevents.