Come on guys, you make me laugh! (no offense intended...)
Ivan, try to understand what Spencer was saying. He just tried to explain (albeit in a real minimalist style ;-) that there is no such IP address that cannot be mapped to a DNS. You can map any IP address to many host names - there are almost endless possibilities. OTOH what you tried to say (at least in my interpretation, correct me if I'm wrong) is that you can not map your IP addresses to a DNS or host file _in a meaningful way_. But that's a completely different story.
If you cannot map your IP addresses in a meaningful way AND you want to use Observium, then you should map your IP addresses in some less meaningful ways. Like host_A.B.C.D => A.B.C.D
If I understood you correctly, in your network you have plenty of IP addresses/ranges that are being associated/used by hosts on an almost random (or some unpredictable) way. And you want to monitor them. What I would like to ask you (and you should ask yourself too), what is network monitoring good for, if you are unable to tell which device was actually monitored at what time? This is the same problem Steve Costaras lined out, and as he told us they have a pretty hard time figuring it out. They are searching for a needle in a haystack while they are not quite sure about the appearance of the needle. :)
So if you want to monitor an IP address that gets picked up by some host, used for a while and then abandoned, and picked up by another host etc... then bite the bullet and create some DNS resolution solution (there were some options mentioned here before) for Observium to be able to handle the situation.
As for your last post: Does a problem exist? Yes, Observium is unable to handle devices by IP address, only by hostname. Does it impose a big obstacle? It depends on the usage pattern, but there are solutions/workarounds etc. for average businesses this makes no problem. Is this a bug or a feature? It is a feature, as this was a design decision, which was taken by Adam, and if you want to use the program you have to live with it. Or try to convince Adam to change it, but as this is a real fundamental thing I really doubt they would be taking it easily.
My 2cents, Tylla
On 2016-05-10 00:12, Ivan Jukic wrote:
That's is you solution. Pretend the issue/problem doesn't exist. Brilliant!!
On 10 May 2016 at 08:08, Spencer Ryan <sryan@arbor.net mailto:sryan@arbor.net> wrote:
There is no such thing. * Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net <mailto:sryan@arbor.net> *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com <http://www.arbornetworks.com/> On Mon, May 9, 2016 at 6:07 PM, Ivan Jukic <ijukic13@gmail.com <mailto:ijukic13@gmail.com>> wrote: Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file? On 10 May 2016 at 07:59, Spencer Ryan <sryan@arbor.net <mailto:sryan@arbor.net>> wrote: "Most of replies seems to think all the devices are unix like boxes" What the devices are, or what OS they run is completely irrelevant to how they are in DNS. * Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net <mailto:sryan@arbor.net> *Arbor Networks* +1.734.794.5033 <tel:%2B1.734.794.5033> (d) | +1.734.846.2053 <tel:%2B1.734.846.2053> (m) www.arbornetworks.com <http://www.arbornetworks.com/> On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic <ijukic13@gmail.com <mailto:ijukic13@gmail.com>> wrote: Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes On 9 May 2016 at 19:16, Steve Costaras <stevecs@chaven.com <mailto:stevecs@chaven.com>> wrote: We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed). Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into. Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table. Simple but gets the job done. On 5/9/2016 2:50 AM, Tom Laermans wrote: > On 09/05/2016 01:57, Ivan Jukic wrote: >> Hostnames are not necessary when monitoring via SNMP, in fact IP >> Addresses are easier. Second we host many IP address ranges for our >> clients (Public and Private), so this will be a nightmare to manage. >> As they tend to change hostnames (and rightly so) all the time. Many >> of them have managed services. > So you are saying you don't know and don't care about what you are > actually monitoring? As it seems they (rightly so, apparently?) swap out > devices daily while keeping them on the same IP address... > > Tom > _______________________________________________ > 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 _______________________________________________ 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