You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π I have found these related issues/pull requests
I had a look I couldn't find any existing feature requests for this.
π·οΈ Feature Request Type
Other
π Feature description
We use uptime-kuma in our organisation to monitor approximately 150 hosts, devices and urls. While searching the friendly name in most scenarios is sufficient to find a specific item sometimes all I have is the IP address. It would be incredibly useful to be able to enter part host name, IP or part of the DNS name for the entry to be able to filter the list and find the result rather than only being able to search via the friendly name.
This also allows potentially quick diagnostics in an outage such as if I search for "10.1.16." the results will show everything in that IP range and we'll quickly allow me to diagnose a problem with that specific subnet or route if I can see multiple devices in that range are offline as compared to other subnets.
βοΈ Solution
Simply adding the hostname and URL Fields as part of the search would solve this. At present you can only search via the friendly name.
β Alternatives
I have considered putting the IP address or the host name into the friendly name but due to the number of items we have trying to keep the friendly names shortened concise is challenging enough without putting the IP address in there as well. It is also duplicating information which could result in somebody updating a hostname when an IP address changes and forgetting to update the friendly name resulting inconsistencies.
π Additional Context
Quite a simple one just looking for the ability to for my team to find the information we need and diagnose the source of an outage quicker than we can currently.
We are small team looking after a very large organisation and we use uptime Kuma because it has an active development and is very simple to set up, use, and manage. Keep up the fantastic work and we also can't wait for V2 for the database performance improvements.
The text was updated successfully, but these errors were encountered:
π I have found these related issues/pull requests
I had a look I couldn't find any existing feature requests for this.
π·οΈ Feature Request Type
Other
π Feature description
We use uptime-kuma in our organisation to monitor approximately 150 hosts, devices and urls. While searching the friendly name in most scenarios is sufficient to find a specific item sometimes all I have is the IP address. It would be incredibly useful to be able to enter part host name, IP or part of the DNS name for the entry to be able to filter the list and find the result rather than only being able to search via the friendly name.
This also allows potentially quick diagnostics in an outage such as if I search for "10.1.16." the results will show everything in that IP range and we'll quickly allow me to diagnose a problem with that specific subnet or route if I can see multiple devices in that range are offline as compared to other subnets.
βοΈ Solution
Simply adding the hostname and URL Fields as part of the search would solve this. At present you can only search via the friendly name.
β Alternatives
I have considered putting the IP address or the host name into the friendly name but due to the number of items we have trying to keep the friendly names shortened concise is challenging enough without putting the IP address in there as well. It is also duplicating information which could result in somebody updating a hostname when an IP address changes and forgetting to update the friendly name resulting inconsistencies.
π Additional Context
Quite a simple one just looking for the ability to for my team to find the information we need and diagnose the source of an outage quicker than we can currently.
We are small team looking after a very large organisation and we use uptime Kuma because it has an active development and is very simple to set up, use, and manage. Keep up the fantastic work and we also can't wait for V2 for the database performance improvements.
The text was updated successfully, but these errors were encountered: