Agreed. I know I gave my opinion before on which IP to display, but that was more just weighing in on that specific component. I don't think there is any real need to have the IP displayed at all.
If it were to go ahead:
Perhaps it could be implemented more like the hover bubbles that are used for port IPs (the ones that go and perform a whois query).
Otherwise, I'd be more inclined to go with only updating that address during a discovery, not during polling. If done during polling and the below timeout scenarios take place *for every device you need to poll*, then your poller likely won't complete and you'll have lost data points. It would still likely clag up your discovery process, but it is less sensitive to overall time.
The trouble then becomes that it'll be hours before the system updates it and somebody will complain that it wasn't instant.
There's actually no real win-win scenario IMO.
Michael
On 9 Nov. 2016, at 8:58 pm, Colin Stubbs colin.stubbs@equatetechnologies.com.au wrote:
A scenario,
Alerts, network outages, stuff hitting fans etc
You got to Observium to work out what has been happening and get to the main web interface ok, but every time you try to view any device details the page load stalls for lookup retries * DNS servers * search domains * 1 second
Resolving that name on page load is not so helpful now eh.
Tom's brainstorm idea would be the way to go. If this is really worth doing.