Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
Where would you put it on the UI?
Adam.
Sent from BlueMail
On 7 Nov 2016, 18:58, at 18:58, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of
the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, November 07, 2016 1:37 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca @tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org @tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
_____
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail
On 7 Nov 2016, 19:45, at 19:45, John Simino jsimino@cityofmesquite.com wrote:
I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, November 07, 2016 1:37 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca @tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org @tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
A single Address on the device page with a hover box possibly? I too would find this useful.
Richard Wigzell Networks, Security and Server Specialist IT Services | University of Oxford 13 Banbury Road, Oxford OX2 6NN
T: 01865 616282 www.it.ox.ac.ukhttps://www.it.ox.ac.uk/
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 07 November 2016 19:58 To: Observium Network Observation System Subject: Re: [Observium] Small feature request
What do you do for a router with 50 addresses? Adam.
Sent from BlueMailhttp://www.bluemail.me/r On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.commailto:jsimino@cityofmesquite.com> wrote: I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, November 07, 2016 1:37 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Small feature request
Where would you put it on the UI? Adam.
Sent from BlueMailhttp://www.bluemail.me/r On 7 Nov 2016, at 18:58, Attila Nagy <memetic.orgmailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.orghttp://memetic.org@tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would
say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
________________________________
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
________________________________
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla ------------------------------------------------------------------------ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Possibly, or the Top 1 or just a placeholder.
Sent from my iPhone
On 7 Nov 2016, at 23:06, Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx> wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote: A single Address on the device page with a hover box possibly? I too would find this useful.
Richard Wigzell Networks, Security and Server Specialist IT Services | University of Oxford 13 Banbury Road, Oxford OX2 6NN
T: 01865 616282 www.it.ox.ac.ukhttps://www.it.ox.ac.uk/
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 07 November 2016 19:58 To: Observium Network Observation System Subject: Re: [Observium] Small feature request
What do you do for a router with 50 addresses? Adam.
Sent from BlueMailhttp://www.bluemail.me/r On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.commailto:jsimino@cityofmesquite.com> wrote: I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, November 07, 2016 1:37 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Small feature request
Where would you put it on the UI? Adam.
Sent from BlueMailhttp://www.bluemail.me/r On 7 Nov 2016, at 18:58, Attila Nagy <memetic.orgmailto:tylla_at_%3ca@tylla.huhttp://tylla.hu target=_blank>tylla_at_memetic.orghttp://memetic.org@tylla.huhttp://tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would
say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
________________________________
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
________________________________
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too
would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data.
If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote:
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Not to take a side in the age old DNS vs IP debate around this software, but;
I think if this feature had to be implemented in a reasonable manner, the IP should simply be the IP that Observium gets when it resolves the DNS name of the device.
Jacob Bisby
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Tuesday, 8 November 2016 1:32 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote:
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Dear all,
+1 to that.
Y.
Le 8 nov. 2016 à 06:44, Jacob Bisby Jacob.Bisby@uniscope.com.au a écrit :
Not to take a side in the age old DNS vs IP debate around this software, but;
I think if this feature had to be implemented in a reasonable manner, the IP should simply be the IP that Observium gets when it resolves the DNS name of the device.
Jacob Bisby
BENGELLOUN - ZAHR Youssef - Consultant Expert Prodware France T : +33 979 999 000 F : +33 988 814 001 - ybzahr@prodware.fr Web : prodware.fr
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Tuesday, 8 November 2016 1:32 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote: My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote: Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote: A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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.
[root@observium includes]# grep -nr 'gethostbyname*' common.inc.php:2736:// Same as gethostbyname(), but work with both IPv4 and IPv6 common.inc.php:2740:// For get only IPv6 record use gethostbyname6($hostname, OBS_DNS_AAAA) common.inc.php:2743:function gethostbyname6($host, $flags = OBS_DNS_ALL) common.inc.php:2750: $dns = gethostbynamel6($host, $flags); common.inc.php:2759:// Same as gethostbynamel(), but work with both IPv4 and IPv6 common.inc.php:2761:// for get only IPv6 addresses use gethostbynamel6($hostname, OBS_DNS_AAAA) common.inc.php:2764:function gethostbynamel6($host, $flags = OBS_DNS_ALL) functions.inc.php:346: $ip = gethostbyname6($new, $flags); functions.inc.php:587: $ip = gethostbyname6($hostname, $flags); functions.inc.php:919: $ip = gethostbyname6($hostname); functions.inc.php:1082: $ip = ($try_a ? gethostbyname($hostname) : FALSE); // Do not check IPv4 if transport IPv6 functions.inc.php:1087: $ip = gethostbyname6($hostname, OBS_DNS_AAAA); functions.inc.php:1208: return (TRUE && gethostbyname6($hostname, $flags)); discovery/functions.inc.php:49: $ip = gethostbyname6($hostname, $flags); discovery/functions.inc.php:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/functions.inc.php:119: $ptr_ip = gethostbyname6($ptr, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:49: $ip = gethostbyname6($hostname, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:119: $ptr_ip = gethostbyname6($ptr, $flags);
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Monday, November 07, 2016 11:32 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote:
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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.
[root@observium includes]# grep -nr 'gethostbyname*' common.inc.php:2736:// Same as gethostbyname(), but work with both IPv4 and IPv6 common.inc.php:2740:// For get only IPv6 record use gethostbyname6($hostname, OBS_DNS_AAAA) common.inc.php:2743:function gethostbyname6($host, $flags = OBS_DNS_ALL) common.inc.php:2750: $dns = gethostbynamel6($host, $flags); common.inc.php:2759:// Same as gethostbynamel(), but work with both IPv4 and IPv6 common.inc.php:2761:// for get only IPv6 addresses use gethostbynamel6($hostname, OBS_DNS_AAAA) common.inc.php:2764:function gethostbynamel6($host, $flags = OBS_DNS_ALL) functions.inc.php:346: $ip = gethostbyname6($new, $flags); functions.inc.php:587: $ip = gethostbyname6($hostname, $flags); functions.inc.php:919: $ip = gethostbyname6($hostname); functions.inc.php:1082: $ip = ($try_a ? gethostbyname($hostname) : FALSE); // Do not check IPv4 if transport IPv6 functions.inc.php:1087: $ip = gethostbyname6($hostname, OBS_DNS_AAAA); functions.inc.php:1208: return (TRUE && gethostbyname6($hostname, $flags)); discovery/functions.inc.php:49: $ip = gethostbyname6($hostname, $flags); discovery/functions.inc.php:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/functions.inc.php:119: $ptr_ip = gethostbyname6($ptr, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:49: $ip = gethostbyname6($hostname, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:119: $ptr_ip = gethostbyname6($ptr, $flags);
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Monday, November 07, 2016 11:32 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote:
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely belisted
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to(mostly
this is that I am eager to know). Yes-yes, I know, DNS solvesmost
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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 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.
[root@observium includes]# grep -nr 'gethostbyname*' common.inc.php:2736:// Same as gethostbyname(), but work with both IPv4 and IPv6 common.inc.php:2740:// For get only IPv6 record use gethostbyname6($hostname, OBS_DNS_AAAA) common.inc.php:2743:function gethostbyname6($host, $flags = OBS_DNS_ALL) common.inc.php:2750: $dns = gethostbynamel6($host, $flags); common.inc.php:2759:// Same as gethostbynamel(), but work with both IPv4 and IPv6 common.inc.php:2761:// for get only IPv6 addresses use gethostbynamel6($hostname, OBS_DNS_AAAA) common.inc.php:2764:function gethostbynamel6($host, $flags = OBS_DNS_ALL) functions.inc.php:346: $ip = gethostbyname6($new, $flags); functions.inc.php:587: $ip = gethostbyname6($hostname, $flags); functions.inc.php:919: $ip = gethostbyname6($hostname); functions.inc.php:1082: $ip = ($try_a ? gethostbyname($hostname) : FALSE); // Do not check IPv4 if transport IPv6 functions.inc.php:1087: $ip = gethostbyname6($hostname, OBS_DNS_AAAA); functions.inc.php:1208: return (TRUE && gethostbyname6($hostname, $flags)); discovery/functions.inc.php:49: $ip = gethostbyname6($hostname, $flags); discovery/functions.inc.php:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/functions.inc.php:119: $ptr_ip = gethostbyname6($ptr, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:49: $ip = gethostbyname6($hostname, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:108: $snmp_ip = gethostbyname6($snmphost, $flags); discovery/.svn/text-base/functions.inc.php.svn-base:119: $ptr_ip = gethostbyname6($ptr, $flags);
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tom Laermans Sent: Monday, November 07, 2016 11:32 PM To: Observium Network Observation System mailto:observium@observium.org observium@observium.org Subject: Re: [Observium] Small feature request
Well, the funny thing is.. Observium doesn't use an IP to query the device on.
See what can of worms you opened? ;-)
Tom
On 08/11/2016 05:52, Michael wrote:
My vote would be for the IP that observium is using to query the device on.
Surely nobody is using round robin dns A records to get to their management IPs...?
In my mind, the rest of the IPs belong on the interface/port that it is bound to.
Cheers,
Michael
On 8 November 2016 10:06:23 am AEDT, Tom Laermans mailto:tom.laermans@powersource.cx tom.laermans@powersource.cx wrote:
Random single address? :)
On 07/11/2016 23:47, Richard Wigzell wrote:
A single Address on the device page with a hover box possibly? I too would find this useful.
*Richard Wigzell* Networks, Security and Server Specialist IT Services | University of Oxford
13 Banbury Road, Oxford OX2 6NN
*T:* 01865 616282 www.it.ox.ac.uk http://www.it.ox.ac.uk https://www.it.ox.ac.uk/ https://www.it.ox.ac.uk/
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* 07 November 2016 19:58 *To:* Observium Network Observation System *Subject:* Re: [Observium] Small feature request
What do you do for a router with 50 addresses?
Adam.
Sent from BlueMail http://www.bluemail.me/r http://www.bluemail.me/r
On 7 Nov 2016, at 19:45, John Simino <jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com mailto:jsimino@cityofmesquite.com> wrote:
I too sometimes look for it on the device page. There is a section
in
the device page that lists Hardware, OS, Name, Location and Uptime.
I
would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System <observium@observium.org mailto:observium@observium.org mailto:observium@observium.org mailto:observium@observium.org> *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be
listed
on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would
say lets display the one that the devices FQDN resolves to
(mostly
this is that I am eager to know). Yes-yes, I know, DNS solves
most
of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla
--------------------------------------------------------------------- ---
observium mailing list observium@observium.org mailto:observium@observium.org mailto:observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--------------------------------------------------------------------- ---
observium mailing list observium@observium.org mailto:observium@observium.org mailto:observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
--------------------------------------------------------------------- ---
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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 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.
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.
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
Brainstorm idea:
During discovery (because poller does not need to do this every 5 minutes, and the web interface definitely should not do this live on page load) we set a device attrib containing the IP, based on the following:
- Depending on tcp/udp vs tcp6/udp6 SNMP configuration, resolve A or AAAA. - Check if resulting IP is part of the ipv[4|6]-addresses discovered on the device
If yes, IP is on the box, if not, it's a lie (DNAT, etc) and we unset the attribute.
If the host resolves to multiple addresses all bets are off, but Observium would likely not handle that very well to begin with.
Tom
On 08/11/2016 18:51, Adam Armstrong wrote:
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 http://www.bluemail.me/r
On 8 Nov 2016, at 17:36, John Simino <jsimino@cityofmesquite.com mailto: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 <observium@observium.org> <mailto: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
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I also wanted an IP address on the device page, so I edited /opt/observium/html/pages/device/overview/information.inc.php and /opt/observium/html/pages/device/overview/information_extended.inc.php to resolve the host name and post the ip.
My device pages look like this:
Hardware: ex4200-24T Operating System: JunOS System name: mydevice Address: 192.168.0.1 Contact: someone Location: somewhere Serial: 123 Uptime: 12 days
Below is the code I added to the files.
///EDIT if ($device['sysName']) { echo('<tr> <td class="entity">System name</td>'); echo(' <td>' . escape_html($device['sysName']). '</td> </tr>');
echo('<tr> <td class="entity">Address</td>'); $S_hostname = $device['hostname']; $S_ip = gethostbyname($S_hostname); echo(' <td>' . escape_html($S_ip). '</td> </tr>'); } //////////
On 11/07/2016 02:45 PM, John Simino wrote:
I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Adam Armstrong *Sent:* Monday, November 07, 2016 1:37 PM *To:* Observium Network Observation System observium@observium.org *Subject:* Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla ------------------------------------------------------------------------ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I too sometimes look for it on the device page. There is a section in the device page that lists Hardware, OS, Name, Location and Uptime. I would add IP address to that section.
It could also be displayed as a Known addresses listing on the main page along with processors, memory, storage, and other tabular data. If there were multiple addresses for a device, they could all be listed in the tabular listing.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Monday, November 07, 2016 1:37 PM To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Small feature request
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3ca @tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org @tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
_____
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy.
As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to.
Exactly as Skyler Blumer resolved it in his small hack.
Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address.
Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler)
That was my 2 cents. Tylla
On 2016-11-07 20:37, Adam Armstrong wrote:
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3Ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla ------------------------------------------------------------------------ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Don't use that patch, doing a DNS lookup for every page load is a bad idea!
Adam.
Sent from BlueMail
On 9 Nov 2016, 00:15, at 00:15, Nagy Attila tylla_at_memetic.org@tylla.hu wrote:
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy.
As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to.
Exactly as Skyler Blumer resolved it in his small hack.
Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address.
Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler)
That was my 2 cents. Tylla
On 2016-11-07 20:37, Adam Armstrong wrote:
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org mailto:tylla_at_%3Ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Hi all! I ran into this small deficit a few times, but now I decided toreport
it, maybe it gets the attention of other fellow users and/or ofdevelopers.
So the small thing that I miss sometimes from the GUI is thedisplay of
the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltipthat
appears when hovering the mouse (let's say after the FQDN insquare
brackets). And given the fact that a device can have many IP addresses, Iwould say
lets display the one that the devices FQDN resolves to (mostlythis is
that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimesit is
just easier if you know the IP address. Any opinions? Regards, Tylla
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It's one DNS lookup when you click on a device page. I don't really see the harm.
On 11/08/2016 08:05 PM, Adam Armstrong wrote:
Don't use that patch, doing a DNS lookup for every page load is a bad idea!
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 9 Nov 2016, at 00:15, Nagy Attila <memetic.org mailto:tylla_at_%3Ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy. As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to. Exactly as Skyler Blumer resolved it in his small hack. Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address. Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler) That was my 2 cents. Tylla On 2016-11-07 20:37, Adam Armstrong wrote:Where would you put it on the UI? Adam. Sent from BlueMail <http://www.bluemail.me/r> On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org <mailto:tylla_at_%3Ca>@tylla.hu target=_blank>tylla_at_memetic.org <http://memetic.org>@tylla.hu> wrote: Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla ------------------------------------------------------------------------ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium------------------------------------------------------------------------ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It would be very helpful to have this feature.
On Wed, 9 Nov 2016 at 02:06 Skyler Blumer skyler.blumer@zitomedia.com wrote:
It's one DNS lookup when you click on a device page. I don't really see the harm.
On 11/08/2016 08:05 PM, Adam Armstrong wrote:
Don't use that patch, doing a DNS lookup for every page load is a bad idea!
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 9 Nov 2016, at 00:15, Nagy Attila <memetic.org <tylla_at_%3Ca>@tylla.hu target=_blank>tylla_at_memetic.org@tylla.hu> wrote:
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy.
As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to.
Exactly as Skyler Blumer resolved it in his small hack.
Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address.
Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler)
That was my 2 cents. Tylla
On 2016-11-07 20:37, Adam Armstrong wrote:
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org <tylla_at_%3Ca>@tylla.hu target=_blank>tylla_at_memetic.org@tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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.
On 9 Nov 2016 12:06 PM, "Skyler Blumer" skyler.blumer@zitomedia.com wrote:
It's one DNS lookup when you click on a device page. I don't really see the harm.
On 11/08/2016 08:05 PM, Adam Armstrong wrote:
Don't use that patch, doing a DNS lookup for every page load is a bad idea!
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 9 Nov 2016, at 00:15, Nagy Attila <memetic.org <tylla_at_%3Ca>@tylla.hu target=_blank>tylla_at_memetic.org@tylla.hu> wrote:
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy.
As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to.
Exactly as Skyler Blumer resolved it in his small hack.
Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address.
Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler)
That was my 2 cents. Tylla
On 2016-11-07 20:37, Adam Armstrong wrote:
Where would you put it on the UI?
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org <tylla_at_%3Ca>@ tylla.hu target=_blank>tylla_at_memetic.org@tylla.hu> wrote:
Hi all!
I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers.
So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know).
Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address.
Any opinions?
Regards, Tylla
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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.
I kinda agree with you, this is not a good solution, the optimal would be doing this DNS lookup in the backend at every poll and storing/updating a field in the database. But as this requires some work/changes on deeper code levels, as a preliminary solution this hack could work. The main problem as I see is a possible delay in the DNS resolution - thus stalling page load - but if this takes more than a few hundred ms than there will be other problems arising as well.
Tylla
On 2016-11-09 02:05, Adam Armstrong wrote:
Don't use that patch, doing a DNS lookup for every page load is a bad idea!
Adam.
Sent from BlueMail http://www.bluemail.me/r
On 9 Nov 2016, at 00:15, Nagy Attila <memetic.org mailto:tylla_at_%3Ca@tylla.hu target=_blank>tylla_at_memetic.org http://memetic.org@tylla.hu> wrote:
Sorry guys, I didn't meant to drop the flame bomb, then disappear and get back much later to see the ruins :))), but I was pretty busy. As I wrote in my original mail I thought about displaying the address in the overview page. And yes I was thinking about strictly displaying the (hopefully only) one IP address that the stored hostname gets resolved to. Exactly as Skyler Blumer resolved it in his small hack. Actually this small hack could be used to solve the issue. It could be hardened if you wish, - like you said - checking that the IP address returned is listed anywhere between some interfaces of the host, but I would say if the SNMP service can be reached on a given IP, then let's assume that you can do something with that device using the same address. Yes of course, there could be complications, and there are a few possible issues that can't be properly taken care of, but an almost perfect solution is way better - if it solves most of the needs - than nothing. And as Skyler's solution shows, the solution is pretty straight forward, I will patch my copy tomorrow. (thanks again Skyler) That was my 2 cents. Tylla On 2016-11-07 20:37, Adam Armstrong wrote:Where would you put it on the UI? Adam. Sent from BlueMail <http://www.bluemail.me/r> On 7 Nov 2016, at 18:58, Attila Nagy <memetic.org <mailto:tylla_at_%3Ca>@tylla.hu target=_blank>tylla_at_memetic.org <http://memetic.org>@tylla.hu> wrote: Hi all! I ran into this small deficit a few times, but now I decided to report it, maybe it gets the attention of other fellow users and/or of developers. So the small thing that I miss sometimes from the GUI is the display of the IP address of a device. In my opinion this information should definitely be listed on the overview page, but optimally it should also appear in the tooltip that appears when hovering the mouse (let's say after the FQDN in square brackets). And given the fact that a device can have many IP addresses, I would say lets display the one that the devices FQDN resolves to (mostly this is that I am eager to know). Yes-yes, I know, DNS solves most of the problems, but sometimes it is just easier if you know the IP address. Any opinions? Regards, Tylla ------------------------------------------------------------------------ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium------------------------------------------------------------------------ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (12)
-
Adam Armstrong -
Attila Nagy -
Colin Stubbs -
Jacob Bisby -
John Simino -
Michael -
Nagy Attila
-
Peter Smith -
Richard Wigzell -
Skyler Blumer -
Tom Laermans -
Youssef BENGELLOUN - ZAHR