mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
A custom command monitor #4278
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#4278
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 @XotEmBotZ on GitHub (Aug 30, 2025).
📑 I have found these related issues/pull requests
Everything considering improving and creating new monitors as it can be acheived by this (till an actual implementation is done)
🏷️ Feature Request Type
New monitor
🔖 Feature description
A custom monitor which runs a command in the server and decides the state based on the output
✔️ Solution
I want a custom monitor which will allow me to run a command in the server and based on the exit code (or output ) the monitor will change its state. Preferably the output of the command will be sent in the notification and be noted down
❓ Alternatives
Presently I have to create a lightweight python http server to do the same and use uptime kuma to do the monitoring which is very tedious.
📝 Additional Context
I (and supposedly many others) sometime needs custom monitoring solution, its very difficult for developers to maintain and update such many monitoring types. Every thing that we need can be done using a terminal so why not create a monitor to run those commands?
Features=>
A very complex logic for monitoring: ✅
A service / protocol which is not supported:✅
A propitiatory thing:✅
Anything too hectic to maintain: ✅
Rejected monitors: ✅
Most of not implemented / under work monitors:✅ (for those who need it fast)