Allow for monitoring a port range #275

Open
opened 2026-02-28 01:41:08 -05:00 by deekerman · 5 comments
Owner

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.

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.
Author
Owner

@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.

@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.
Author
Owner

@Genc commented on GitHub (Jan 7, 2024):

This is no longer necessary. Can we close issue? @louislam

@Genc commented on GitHub (Jan 7, 2024): This is no longer necessary. Can we close issue? @louislam
Author
Owner

@CommanderStorm commented on GitHub (Jan 7, 2024):

This is no longer necessary. Can we close issue?

Why is this no longer necessary? @Genc

@CommanderStorm commented on GitHub (Jan 7, 2024): > This is no longer necessary. Can we close issue? Why is this no longer necessary? @Genc
Author
Owner

@Genc commented on GitHub (Jan 7, 2024):

Bu artık gerekli değil. Konuyu kapatabilir miyiz?

Bu neden artık gerekli değil?@Genc

In fact, it is a request that can be resolved with more than one definition using group monitors. @CommanderStorm

@Genc commented on GitHub (Jan 7, 2024): > > Bu artık gerekli değil. Konuyu kapatabilir miyiz? > > Bu neden artık gerekli değil?@Genc In fact, it is a request that can be resolved with more than one definition using group monitors. @CommanderStorm
Author
Owner

@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

@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
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#275
No description provided.