Feature Description
It would be valuable to display the server’s public IP address in the Instance Monitoring tab.
Currently, the agent displays a local or Docker network address, such as 192.168.x.x or 172.x.x.x. While the local address is useful, it does not identify the server’s public Internet connection.
Ideally, the interface could display both:
Local IP address
Public IP address
This would be especially useful when monitoring servers across multiple locations, remote NAS devices, or hosts behind different Internet connections.
For servers behind the same router or NAT gateway, displaying the same public IP would also make their shared network location easier to identify.
Motivation
When managing servers across multiple sites, the local IP address alone is not enough to identify the Internet connection used by each instance. Displaying the public IP would make troubleshooting, remote access verification, network identification, and infrastructure management easier.
Showing both the local and public IP addresses would provide a more complete view of each monitored server, especially for NAS devices, home labs, remote offices, and servers behind NAT.
Alternatives Considered
No response
Additional Context
No response
Checklist
Feature Description
It would be valuable to display the server’s public IP address in the Instance Monitoring tab.
Currently, the agent displays a local or Docker network address, such as 192.168.x.x or 172.x.x.x. While the local address is useful, it does not identify the server’s public Internet connection.
Ideally, the interface could display both:
Local IP address
Public IP address
This would be especially useful when monitoring servers across multiple locations, remote NAS devices, or hosts behind different Internet connections.
For servers behind the same router or NAT gateway, displaying the same public IP would also make their shared network location easier to identify.
Motivation
When managing servers across multiple sites, the local IP address alone is not enough to identify the Internet connection used by each instance. Displaying the public IP would make troubleshooting, remote access verification, network identification, and infrastructure management easier.
Showing both the local and public IP addresses would provide a more complete view of each monitored server, especially for NAS devices, home labs, remote offices, and servers behind NAT.
Alternatives Considered
No response
Additional Context
No response
Checklist