In the Agent Monitor card, the IP column shows loopback addresses and other random IP addresses instead of the external IP address of the instance.
- Workload type: private and public cloud, hosted instances.
The IP address that appears under the Agent Monitor card is not the externalIP of the instance. It is the first IP of one of the interfaces.
Here's how the IP address is selected:
- If the instance has an interface eth0, its first IP address is used in the Agent Monitor card.
- If the instance has NO eth0 interface, the interfaces are sorted alphabetically and the first IP of the first interface in the list is picked and reported in the Agent Monitor card. That’s why for some instances, you see docker0 IP or the loopback interface IP as the instance IP address.
It is also important to note that the ‘ExternalIP’ tag has no bearing on the IP address in the Agent Monitor card. Usually, it comes from the metadata of the instance in the case of the public cloud.
For on-prem or if the agent fails to retrieve it, it would be set to ‘NOT_AVAILABLE’. If you set it manually as a tag, you can just use it as a search label.