mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Allow for monitoring a port range #275
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#275
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 @djbr22 on GitHub (Sep 27, 2021).
Is it a duplicate question?
no
Is your feature request related to a problem? Please describe.
Not really a problem, but I'd like the ability to monitor multiple ports from the same monitor. I.e. - monitor a range of ports.
Describe the solution you'd like
Either allow me to set a port range (16000-16002) in the TCP/Port field, or allow me to add multiple ports to a monitor (TCP Port 16000, TCP Port 16001, etc). Optionally would like the notification to specify which port went down.
Describe alternatives you've considered
Currently I have to create multiple monitors for the same IP and give each monitor a unique name like Application-16000, Application-16001, etc.
Additional context
Useful for single applications that use multiple ports. It would reduce the number of monitors displayed on my Status Page.
@deefdragon commented on GitHub (Oct 10, 2021):
This would likely be best done via #639 or #549 with the creation of subgroups/collections. Unfortunately each monitor would still be individual. There may be a shortcut for creating subgroups/collections in the future if they get added however, adding all the checks at once.
@Genc commented on GitHub (Jan 7, 2024):
This is no longer necessary. Can we close issue? @louislam
@CommanderStorm commented on GitHub (Jan 7, 2024):
Why is this no longer necessary? @Genc
@Genc commented on GitHub (Jan 7, 2024):
In fact, it is a request that can be resolved with more than one definition using group monitors. @CommanderStorm
@CommanderStorm commented on GitHub (Jan 7, 2024):
While it can be implemented this way, I think the issue is pretty clear in that it wants at least a shortcut for creating this group
=> not resolved