Joseph,
The customer premisses equipment (CPE) are managed and accessed internally for monitoring and maintenance of customer internet connection. Customers are not eternal.
Can you imagine to a system administrator expends all the day adding hostnames in a DNS Server for at least 10 CPE per day that can be changed 2 days after or a weekend after? Or even adding hostnames in the /etc/hosts for five devices that will be removed after 6 hours?
We have system that only needs a screw to be adjusted, and people with the screwdriver in the hand. Are you asking me to search for a screwdriver and reach the screw to be adjusted?
All the service providers I know, does not control CPE units with hostnames. They use hostnames for servers, main routers, main switches, and other devices that are usually in the Data Center.
Em seg, 9 de mai de 2016 às 16:47, observium-request@observium.org escreveu:
Send observium mailing list submissions to observium@observium.org
To subscribe or unsubscribe via the World Wide Web, visit http://postman.memetic.org/cgi-bin/mailman/listinfo/observium or, via email, send a message with subject or body 'help' to observium-request@observium.org
You can reach the person managing the list at observium-owner@observium.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of observium digest..."
Today's Topics:
- Re: observium Digest, Vol 70, Issue 42 (Joseph Zancocchio)
Message: 1 Date: Mon, 9 May 2016 15:47:13 -0400 From: Joseph Zancocchio joseph@nyi.net To: observium@observium.org Subject: Re: [Observium] observium Digest, Vol 70, Issue 42 Message-ID: 5730E941.9010400@nyi.net Content-Type: text/plain; charset="utf-8"; Format="flowed"
It is one time, unless your organization's public IP allocations are regularly changing.... (I am asusming, of course, that you would take care of all your RFC 1918 subnets at one time, but if more come into use, you could add still add them without any effort at all)
If these "CPE" devices are using a public IP address that your organization doesn't control, then yes, you would have to add internal hosts entries for any such IP(s) that you care about.
But again, a script can do this in a split second, and could easily be written to take a CIDR-syntaxed subnet argument...
This sort of "limitation" should never halt an ISP in its tracks. I mean, Observium is open source.... there is nothing stopping you from patching it directly to do what you want, and maintaining said patch, so if that scenario fits your use case (temporarily monitoring equipment living on public IPs of other organizations), then it sure would make sense to customize your Observium setup to work with it, if maintaining a DNS server or hosts file is too much work for you.
See the license snippet:
|4. You may make modifications to the Software. The following restrictions apply to modifications: a. Modifications must not alter or remove any copyright or identifying notices in the Software. b. You may not distribute modifications in any form except to submit your changes to the copyright holders for inclusion in the Software.|On 05/09/2016 02:03 PM, Claudionei Mendes wrote:
That's the problem. It's not once. It's not one time in life. It's not advanced users that only uses the system.
Can you think on this scenario?
Who uses the information, and who uses the system?
Is it necessary to be an system administrator or a network Engineering to uses the system? Or my Help Desk team will be able to add an CPE for monitoring too?
You are developing a system for big ISP and big companys, but thinking small.
Em seg, 9 de mai de 2016 às 14:26, <observium-request@observium.org mailto:observium-request@observium.org> escreveu:
Send observium mailing list submissions to observium@observium.org <mailto:observium@observium.org> To subscribe or unsubscribe via the World Wide Web, visit http://postman.memetic.org/cgi-bin/mailman/listinfo/observium or, via email, send a message with subject or body 'help' to observium-request@observium.org <mailto:observium-request@observium.org> You can reach the person managing the list at observium-owner@observium.org <mailto:observium-owner@observium.org> When replying, please edit your Subject line so it is more specific than "Re: Contents of observium digest..." Today's Topics: 1. Re: Could not resolve (Spencer Ryan)
Message: 1 Date: Mon, 9 May 2016 13:25:46 -0400 From: Spencer Ryan <sryan@arbor.net <mailto:sryan@arbor.net>> To: Observium Network Observation System <observium@observium.org <mailto:observium@observium.org>> Subject: Re: [Observium] Could not resolve Message-ID: <CA+HzidTFxhKcf16-=xXJZsZNKNyC-MHYX4w=2xSkjUAwcT5K4w@mail.gmail.commailto:2xSkjUAwcT5K4w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8" 10 minutes, one script to add all the names to /etc/hosts You've spent more time explaining why you don't want to do it thanyou
could have just doing it. *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 1:24 PM, Claudionei Mendes < claudionei.mendes@gmail.com <mailto:claudionei.mendes@gmail.com>> wrote: > I don't think it's my personal option. It's a use case that many Service > Providers as us, have. > > You have two Scenarios that are not that simple as it looks. > > We have important devices. Ok. We need host names, but and for temporary > devices, as an CPE. > > Can you imagine the work you are giving to us? Or to any ISP that cares > about the customer? > > It's impossible that only us, as ISP serve temporary events. Don't you > think? > > In my opinion, and it's not hard to implement, you should think in this > scenarios. It won't cost nothing to have both options, IP and Host name. > > Every monitoring system you search, won't have this limitation. > > Adam. It's not my problem. It's what you said. It's a different scenario > that is not implemented in the system. > > Can't you see how many people are complaining about this issue? > > Observium is a great software as I could see until now. Congratulations, > > But, please, think about this situation. In three days there are three > people having this difficult. How many people, do you think, simply have > given up thinking it's a bug on the software, just because, sometimes it > add devices by IP and sometimes it cannot solve the host name? > > Many customers do not complain, they simply turn around and goaway.
> Does that complain, it's because really like your work, and wantsit
> better. > > > > > Em seg, 9 de mai de 2016 às 13:50, <observium-request@observium.org <mailto:observium-request@observium.org>> > escreveu: > >> Send observium mailing list submissions to >> observium@observium.org <mailto:observium@observium.org> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> or, via email, send a message with subject or body 'help' to >> observium-request@observium.org <mailto:observium-request@observium.org> >> >> You can reach the person managing the list at >> observium-owner@observium.org <mailto:observium-owner@observium.org> >> >> When replying, please edit your Subject line so it is morespecific
>> than "Re: Contents of observium digest..." >> >> >> Today's Topics: >> >> 1. Re: Could not resolve (Adam Armstrong) >> 2. Re: Could not resolve (Jason Vanlandingham) >> >> >>
>> >> Message: 1 >> Date: Mon, 09 May 2016 17:46:01 +0100 >> From: Adam Armstrong <adama@memetic.org <mailto:adama@memetic.org>> To: Observium Network Observation System <observium@observium.org <mailto:observium@observium.org>> >> Cc: Observium Network Observation System <observium@observium.org <mailto:observium@observium.org>> >> Subject: Re: [Observium] Could not resolve >> Message-ID: <4cb3a4d0-90e5-46d8-be2d-b8f84bfd0b47@typeapp.com <mailto:4cb3a4d0-90e5-46d8-be2d-b8f84bfd0b47@typeapp.com>> >> Content-Type: text/plain; charset="utf-8" >> >> You're trying very hard to come up with scenarios that people have >> already given you solutions for. >> >> Observium's target market is primarily service providers and enterprise >> with large networks. >> >> Many of our SP customers like the features we have which enforce good >> operational practice. >> >> If Observium works for you and you're not in that segment, that's fine. >> >> However, we can't and won't compromise SP-centric design decisions >> because users outside of our target market don't like them. >> >> Write a script which takes an Ip, puts a dummy entry in to /etc/hosts and >> adds the dummy entry. 5 seconds, done. >> >> It's you who need to solve the problem of your unusual use case, not us >> who need to accommodate it. >> >> There is actually a way to trick Observium in to allowing you to add by >> IP. I use it for temporary devices, and it most definitely involves DNS. ;) >> >> Adam. >> >> Sent from BlueMail >> >> >> >> On May 9, 2016, 17:37, at 17:37, Claudionei Mendes < >> claudionei.mendes@gmail.com <mailto:claudionei.mendes@gmail.com>> wrote: >> >Hello Everybody, >> > >> >I would like to give an example, and I want, mainly the developers of >> >observium to think well on this situation. >> > >> >We often serve temporary events arround, and we need to add this >> >devices >> >for monitoring in somewhere. >> > >> >Now imagine, every weekend, add to host files, IP address to temporary >> >devices. Ok, use always the same IP. Right. >> > >> >In one event we use 5 devices, in another 8. >> > >> >And what if we have 2 or more events at the same time? >> > >> >What if my DNS server, that is a monitored server as well fails? >> > >> >All my monitoring will stop? >> > >> >IP address is faster and more reliable than Hostnames. >> > >> >I would like you to think about adding devices just by hostname. We >> >have >> >3000 devices on the network that we would like to add. But none of them >> >need registered hostname. For this we have SNMP. They are end devices. >> >They >> >need to be monitored to order history and reports, but do not need DNS >> >Names. >> > >> >Important devices have the hostname on the DNS, but anymonitoring
>> >services >> >we used before, we added the devices by hostname. IP is faster. >> > >> > >> > >> >Em sáb, 7 de mai de 2016 às 21:31, <observium-request@observium.org <mailto:observium-request@observium.org>> >> >escreveu: >> > >> >> Send observium mailing list submissions to >> >> observium@observium.org <mailto:observium@observium.org> >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >> >> or, via email, send a message with subject or body 'help' to >> >> observium-request@observium.org <mailto:observium-request@observium.org> >> >> >> >> You can reach the person managing the list at >> >> observium-owner@observium.org <mailto:observium-owner@observium.org> >> >> >> >> When replying, please edit your Subject line so it is more specific >> >> than "Re: Contents of observium digest..." >> >> >> >> >> >> Today's Topics: >> >> >> >> 1. Could not resolve (Nurbek Suleimanov) >> >> 2. Re: Could not resolve (ron@rjr-services.com <mailto:ron@rjr-services.com>) >> >> 3. Re: Could not resolve (Nurbek Suleimanov) >> >> 4. Monitor and bill for VM's in VMWare (Anthony Polselli) >> >> >> >> >> >> >>
>> >> >> >> Message: 1 >> >> Date: Sat, 07 May 2016 19:01:38 +0300 >> >> From: Nurbek Suleimanov <nurbek@suleimanov.org <mailto:nurbek@suleimanov.org>> >> >> To: observium@observium.org <mailto:observium@observium.org> >> >> Subject: [Observium] Could not resolve >> >> Message-ID: <1462636898.127896886@f371.i.mail.ru <mailto:1462636898.127896886@f371.i.mail.ru>> >> >> Content-Type: text/plain; charset="utf-8" >> >> >> >> >> >> Hi, >> >> I want to add the host , and Oservium said Could not resolve >> >10.30.1.1 >> >> I check fping & snmp as writed your side. >> >> >> >> http://www.observium.org/docs/add_device/#troubleshooting >> >> >> >> It all work, w hat could be the reason >> >> >> >> Thanks >> >> >> >> >> >> Best regard, Suleimanov Nurbek >> >> >> >>