Those things you grepped for are verifications done during device addition.
Observium doesn't know and doesn't care what the Ip addresses of the device are during polling and discovery.
I fear you're missing the whole point, which is that we don't currently have any way of knowing what the "main" Ip of a device is, so rather than it just being a case of displaying something we already know, we would actually have to define the method of acquiring the information to begin with.
The closest anyone has come to a sensible idea is to display the Ip resolved from the hostname Observium uses, since it's probably 95% likely this is the IP the device would be known by.
Still, in the real world anything beyond a simple server or basic switch is likely to have multiple IPs, so in many cases the NMS's management Ip may not be a useful Ip to display.
Then you come to the question of why we would risk displaying potentially misleading information when it's many times easier just to refer to devices by hostnames, and look at the ports list if you need an Ip address.
"Hey, I'll just copy the address from the Observium overview page into the ACL... ... Shit."
Human error-related failures from this sort of event are not something we want to encourage.
If the information is needed, get it from the place where you know it's correct, rather than a vague approximation that we've chosen because it's probably maybe mostly accuratish.
And then, there's NAT and IPv6.
Adam.
Sent from BlueMail
On 8 Nov 2016, 17:36, at 17:36, John Simino jsimino@cityofmesquite.com wrote:
Just because the IP is not stored, doesn’t mean Observium does not use it. Arguing that a TCP/IP communication device doesn’t us IP is an idiots argument.And with that, I’ll go back to lurking because its not worth wasting my breath.
Another vote for displaying the resolved IP address of the device as part of the device page.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Tuesday, November 08, 2016 11:27 AM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Ok, that data is not stored at all, so yes, Observium does not use IP addresses. You can keep arguing all you want, and it's totally irrelevant to the mail thread anyway, but Observium does not use IP addresses as such to communicate with devices.
Tom
On 08/11/2016 17:42, John Simino wrote:
I’m not arguing with you about what value you pass as data to a function. I am arguing that the ip is available as data, it is gathered at several points as evidenced by the use of the php function gethostbyname.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Tuesday, November 08, 2016 10:21 AM To: Observium Network Observation System mailto:observium@observium.org observium@observium.org Subject: Re: [Observium] Small feature request
Sorry, we really don't use IP addresses. We pass the hostname as configured to the snmpget/walk/... functions.
Tom
On 11/08/2016 02:48 PM, John Simino wrote:
Well, the funnier thing is...Observium can't talk to anything without IP so this argument doesn’t go very far. Look, I'm not challenging the religion of Observium. I actually don’t mind that it wants to use hostnames. Its cleaner and clearer. But it’s a false argument that Observium doesn’t use IP addresses.
Several functions are going to great lengths to obtain the piece of information. It just needs to be recorded and displayed.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium