- observium - lists.observium.org

How to exclude some network interfaces?
by Sam Munzani 22 Apr '13

22 Apr '13

Hi, I deployed Observium over the weekend to try out. Reading through documents, I figured out how to exclude specific interface types. However trying to figure out how to exclude a specific interface? E.g. The list might be Fa0/30, Fa0/37, Gig0/9, Gig0/42. No contiguous interface. Thanks in advance, Sam

4 3

Observium VMs wrong OS version
by observium＠velder.li 21 Apr '13

21 Apr '13

Hi there In the virtual machine overview (ESXi Host..), the os version is not correct. I added the VM to observium, when squeeze 6.0.6 was installed. Now it is 6.0.7 (since a few weeks) but observium still says 6.0.6. Is that a bug? Regards, Patrick

2 2

IPMI weirdness
by Robert Williams 21 Apr '13

21 Apr '13

Hi All, For a while now it appears that all our devices which also have IPMI cards are seeing every single sensor added and deleted (in that order) on every poll. A relevant snippet from the debug of one device gives: (319ms) Discover sensor: temperature, Array, , 1, ipmi, System Temp, 1 , 1, -7.000, -5.000, 80.000, 85.000, 31.000 , ipmi, , , , SQL[SELECT COUNT(sensor_id) FROM `sensors` WHERE `poller_type`= 'ipmi' AND `sensor_class` = 'temperature' AND `device_id` = '190' AND sensor_type = 'ipmi' AND `sensor_index` = '1'] SQL[INSERT INTO `sensors` (`poller_type`,`sensor_class`,`device_id`,`sensor_oid`,`sensor_index`,`sensor_type`,`sensor_descr`,`sensor_divisor`,`sensor_multiplier`,`sensor_limit`,`sensor_limit_warn`,`sensor_limit_low`,`sensor_limit_low_warn`,`entPhysicalIndex`,`entPhysicalIndex_measured`,`measured_class`,`measured_entity`) VALUES ('ipmi','temperature','190','','1','ipmi','System Temp','1','1','85.000','80.000','-7.000','-5.000','','','','')] ( 223532 inserted ) + SQL[INSERT INTO `eventlog` (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES ('190','NULL','sensor',NOW(),'Sensor Added: temperature ipmi 1 System Temp')] Discover sensor: temperature, Array, , 2, ipmi, Peripheral Temp, 1 , 1, -7.000, -5.000, 80.000, 85.000, 37.000 , ipmi, , , , SQL[SELECT COUNT(sensor_id) FROM `sensors` WHERE `poller_type`= 'ipmi' AND `sensor_class` = 'temperature' AND `device_id` = '190' AND sensor_type = 'ipmi' AND `sensor_index` = '2'] SQL[INSERT INTO `sensors` (`poller_type`,`sensor_class`,`device_id`,`sensor_oid`,`sensor_index`,`sensor_type`,`sensor_descr`,`sensor_divisor`,`sensor_multiplier`,`sensor_limit`,`sensor_limit_warn`,`sensor_limit_low`,`sensor_limit_low_warn`,`entPhysicalIndex`,`entPhysicalIndex_measured`,`measured_class`,`measured_entity`) VALUES ('ipmi','temperature','190','','2','ipmi','Peripheral Temp','1','1','85.000','80.000','-7.000','-5.000','','','','')] ( 223533 inserted ) + SQL[INSERT INTO `eventlog` (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES ('190','NULL','sensor',NOW(),'Sensor Added: temperature ipmi 2 Peripheral Temp')] Discover sensor: fanspeed, Array, , 4, ipmi, FAN, 1 , 1, 450.000, 600.000, 18975.000, 19050.000, 3150.000 , ipmi, , , , <Repeats for all sensors> …(Section cropped)… <Then the removals follow immediately afterwards> SQL[SELECT * FROM sensors AS S, devices AS D WHERE S.sensor_class='voltage' AND S.device_id = D.device_id AND D.device_id = '190' AND S.poller_type = 'ipmi'] - SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223535'] SQL[INSERT INTO `eventlog` (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 5 Vcore')] - SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223536'] SQL[INSERT INTO `eventlog` (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 6 3.3VCC')] - SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223537'] SQL[INSERT INTO `eventlog` (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 7 12V')] - SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223538'] From what I can tell, it’s doing this for all devices with IPMI, regardless of make / model etc. - and it is only doing it to the IPMI sensors, nothing else is affected. Feedback / suggestions welcome! Cheers :) Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

4 4

Re: [Observium] Reset disk storage values on host
by Adam Armstrong 21 Apr '13

21 Apr '13

Output from discovery for that host with -m storage -d Andrew Lynch <lurch89(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

Re: [Observium] Reset disk storage values on host
by Adam Armstrong 21 Apr '13

21 Apr '13

Run discovery. Andrew Lynch <lurch89(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

Reset disk storage values on host
by Andrew Lynch 21 Apr '13

21 Apr '13

I recently changed the disk configuration on one of my monitored hosts. It seems like the discovery engine is pulling the stats incorrectly and applying them to the wrong disks. Is there an easy way (save for removing and re-adding the entire host) to flush the stats of the storage only? I don't care if it has to completely start from scratch. Thanks! -Andy -- Andrew Lynch (KD0IOE) lurch89(a)gmail.com http://andrewrlynch.com "Scientists study the world as it is; engineers create the world that has never been." —Theodore von Kármán WC

1 0

Subifs no longer showing up for Cisco ASR9K/IOS-XR device after upgrade
by Stephen Fulton 21 Apr '13

21 Apr '13

Hi all, I've been using Observium since January, and I've mostly been happy with it. I upgraded to 0.13.4.3934 yesterday, and since then, none of the sub-interfaces on a ASR9K/IOS-XR 4.3.0 router are being collected. Originally I thought it was due to an upgrade error on my part, so I deleted the host and re-added it, but the sub-interfaces are not being seen and data not being collected. Let me know what information is needed, and I'll present it. -- Stephen

1 0

Re: [Observium] IPMI weirdness
by Robert Williams 21 Apr '13

21 Apr '13

Dear Tom, Pretty please? If you get it working again, at the end there will be cake... :) -----Original Message----- From: observium-bounces(a)observium.org [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: 20 April 2013 21:44 To: Observium Network Observation System Subject: Re: [Observium] IPMI weirdness You need to be extra nice to Tom, as the IPMI stuff is written by him :) adam. On 2013-04-20 21:25, List User wrote: > I posted this earlier (as did a couple of other people) but it was > never fixed. > > On 4/20/2013 6:33 AM, Robert Williams wrote: > > Hi All, > > For a while now it appears that all our devices which also have IPMI > cards are seeing every single sensor added and deleted (in that order) > on every poll. > > A relevant snippet from the debug of one device gives: > > (319ms) Discover sensor: temperature, Array, , 1, ipmi, System Temp, 1 > , 1, -7.000, -5.000, 80.000, 85.000, 31.000 , ipmi, , , , > > SQL[SELECT COUNT(sensor_id) FROM `sensors` WHERE `poller_type`= 'ipmi' > AND `sensor_class` = 'temperature' AND `device_id` = '190' AND > sensor_type = 'ipmi' AND `sensor_index` = '1'] > > SQL[INSERT INTO `sensors` > (`poller_type`,`sensor_class`,`device_id`,`sensor_oid`,`sensor_index`, > `sensor_type`,`sensor_descr`,`sensor_divisor`,`sensor_multiplier`,`sen > sor_limit`,`sensor_limit_warn`,`sensor_limit_low`,`sensor_limit_low_wa > rn`,`entPhysicalIndex`,`entPhysicalIndex_measured`,`measured_class`,`m > easured_entity`) VALUES > ('ipmi','temperature','190','','1','ipmi','System > Temp','1','1','85.000','80.000','-7.000','-5.000','','','','')] ( > 223532 inserted ) > > + > > SQL[INSERT INTO `eventlog` > (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES > ('190','NULL','sensor',NOW(),'Sensor Added: temperature ipmi 1 System > Temp')] Discover sensor: temperature, Array, , 2, ipmi, Peripheral > Temp, 1 , 1, -7.000, -5.000, 80.000, 85.000, 37.000 , ipmi, , , , > > SQL[SELECT COUNT(sensor_id) FROM `sensors` WHERE `poller_type`= 'ipmi' > AND `sensor_class` = 'temperature' AND `device_id` = '190' AND > sensor_type = 'ipmi' AND `sensor_index` = '2'] > > SQL[INSERT INTO `sensors` > (`poller_type`,`sensor_class`,`device_id`,`sensor_oid`,`sensor_index`, > `sensor_type`,`sensor_descr`,`sensor_divisor`,`sensor_multiplier`,`sen > sor_limit`,`sensor_limit_warn`,`sensor_limit_low`,`sensor_limit_low_wa > rn`,`entPhysicalIndex`,`entPhysicalIndex_measured`,`measured_class`,`m > easured_entity`) VALUES > ('ipmi','temperature','190','','2','ipmi','Peripheral > Temp','1','1','85.000','80.000','-7.000','-5.000','','','','')] ( > 223533 inserted ) > > + > > SQL[INSERT INTO `eventlog` > (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES > ('190','NULL','sensor',NOW(),'Sensor Added: temperature ipmi 2 > Peripheral Temp')] Discover sensor: fanspeed, Array, , 4, ipmi, FAN, 1 > , 1, 450.000, 600.000, 18975.000, 19050.000, 3150.000 , ipmi, , , , > > <Repeats for all sensors> > > …(Section cropped)… > > <Then the removals follow immediately afterwards> > > SQL[SELECT * FROM sensors AS S, devices AS D WHERE > S.sensor_class='voltage' AND S.device_id = D.device_id AND D.device_id > = '190' AND S.poller_type = 'ipmi'] - > > SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223535'] > > SQL[INSERT INTO `eventlog` > (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES > ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 5 Vcore')] > - > > SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223536'] > > SQL[INSERT INTO `eventlog` > (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES > ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 6 3.3VCC')] > - > > SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223537'] > > SQL[INSERT INTO `eventlog` > (`device_id`,`reference`,`type`,`timestamp`,`message`) VALUES > ('190','NULL','sensor',NOW(),'Sensor Deleted: voltage ipmi 7 12V')] - > > SQL[DELETE FROM `sensors` WHERE `sensor_id` = '223538'] > > From what I can tell, it's doing this for all devices with IPMI, > regardless of make / model etc. - and it is only doing it to the IPMI > sensors, nothing else is affected. > > Feedback / suggestions welcome! > > Cheers :) > > Robert Williams > Custodian Data Centre > Email: Robert(a)CustodianDC.com > http://www.CustodianDC.com [2] > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1] > > > > Links: > ------ > [1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > [2] http://www.CustodianDC.com > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Re: [Observium] observium post from ronbobius@gmail.com requires approval
by Adam Armstrong 20 Apr '13

20 Apr '13

> What I have done with some 'very important' devices is do just that. > Change the cron entry for specific entries to 1 minute. > > Would this break anything Adam? These are smaller Cisco devices with > few interfaces. > It won't do anything, because the RRD won't store more than one data point every 300 seconds. If you changed the RRD databases, they'd stop storing the normal datapoints, because they would be at the wrong resolution. Like I said, it can't currently be done. You could change the entire installation to be 1-minute, change the RRD template and delete all of the existing RRDs, but you wouldn't want to, because that would be a lot of load on your network and on the observium host. Also, your changes would likely be overwritten by a future update, then you'd be stuffed :) adam.

1 0

Observium Enterprise/Pro licensing
by Adam Armstrong 19 Apr '13

19 Apr '13

Hi All, At some point in the future it's likely that I'm going to split Observium into free and enterprise/pro variants. Observium has historically been developed as a fairly ad hoc project, with work being done as time permits between work projects. We've often had gaps of 6 months where there has been little work done due to other commitments. As the user-base expands this is going to become less and less viable a way of maintaining the project, and we need to be able to devote more time to keeping on top of bug reports and feature development. To be able to devote more time to the project we need to establish a revenue stream to be able to support it. We'd like comments from you guys about how we should go about splitting, what should be in each version, and what we should charge. We're considering: A hosts/ports-based licensing scheme, where you get a certain number free, and any more than that requires a license. A feature-based licensing scheme, where higher-value features such as load balancers, netapp, mac accounting, vpn tracking, etc require a license. Licensing for customer-access, where allowing customers access to the web interface requires a license. What pricing models do you think would work? Options for the ent/pro version include using the honour system, maintaining a separate password-protected SVN repository or distributing an ioncube-protected version. I would prefer to go the honour system route, but I'm not sure how well that would work. Thanks, adam.

16 29