- observium - lists.observium.org

Issue with 95th Percentile for Billing
by Poh Yong Hwang 23 Apr '13

23 Apr '13

Hi All, New here. :) I have an issue with the billing of traffic. I want to bill according to 95th percentile but for some reason it is always 0Mbps. It can plot my traffic for incoming and outgoing but it always show 0 for my 95th percentile. Any advise on this? Thanks Poh

2 1

Re: [Observium] Issue with 95th Percentile for Billing
by Adam Armstrong 23 Apr '13

23 Apr '13

You are not running the billing poller. Poh Yong Hwang <yongsan(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Re: [Observium] Strange timezone behaviour in graphs
by Adam Armstrong 23 Apr '13

23 Apr '13

Still irritating, though. Matt Hucker <matt(a)nrsolutions.com.au> wrote: >Cool. Easy enough to work around. > >Thanks, >Matt > > >On 23/04/2013, at 2:28 PM, Adam Armstrong wrote: > >> Yes. This is down to some funkiness with timezones between client and server. >> >> It has been known for a while. The last attempted fix was reverted because it broke things even more! >> >> Adam. >> >> Matt Hucker <matt(a)nrsolutions.com.au> wrote: >> >>> Hi, >>> >>> I'm not sure what to make of this. When I try to enter custom time ranges in any of the traffic graphs, I get different results depending on which browser I'm using. >>> >>> Results are as follows. I'm in Brisbane (GMT +10). >>> >>> Mac OS X 10.6 >>> >>> Firefox: Observium always converts the time I enter (in local time) to GMT. Therefore my graphs are out by 10 hours. >>> Safari: Won't accept any time info I enter. Always give me the last 24 hours. >>> Chrom: Everything seems to work ok. >>> >>> Windows 7 >>> >>> Internet Explorer: Always gives me the last 24 hours. Same as Safari on OS X >>> Chrome: Everything seems ok. >>> >>> >>> Clicking any of the preset time periods, e.g 6 / 24 / 48 hours, always works ok regardless of which browser/os I'm using. >>> >>> Is this expected behaviour? >>> >>> Cheers, >>> Matt. >>> _______________________________________________ >>> 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 > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Re: [Observium] Strange timezone behaviour in graphs
by Adam Armstrong 23 Apr '13

23 Apr '13

Yes. This is down to some funkiness with timezones between client and server. It has been known for a while. The last attempted fix was reverted because it broke things even more! Adam. Matt Hucker <matt(a)nrsolutions.com.au> wrote: >Hi, > >I'm not sure what to make of this. When I try to enter custom time ranges in any of the traffic graphs, I get different results depending on which browser I'm using. > >Results are as follows. I'm in Brisbane (GMT +10). > >Mac OS X 10.6 > >Firefox: Observium always converts the time I enter (in local time) to GMT. Therefore my graphs are out by 10 hours. >Safari: Won't accept any time info I enter. Always give me the last 24 hours. >Chrom: Everything seems to work ok. > >Windows 7 > >Internet Explorer: Always gives me the last 24 hours. Same as Safari on OS X >Chrome: Everything seems ok. > > >Clicking any of the preset time periods, e.g 6 / 24 / 48 hours, always works ok regardless of which browser/os I'm using. > >Is this expected behaviour? > >Cheers, >Matt. >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

Re: [Observium] Changes made to Devices > Locations
by Adam Armstrong 23 Apr '13

23 Apr '13

There is still work to be done on it. The geolocation service we are using is a little temperamental, so needs well formatted locations. Adam. Paul Gear <observium(a)gear.dyndns.org> wrote: >On 04/23/2013 02:17 PM, Sonny Kupka wrote: >> Tom, >> >> Worked perfectly. >> >> Thanks. >> Sonny >> >> >> ----- Original Message ----- >> From: "Tom Laermans" <tom.laermans(a)powersource.cx> >> To: "Observium Network Observation System" <observium(a)observium.org> >> Sent: Monday, April 22, 2013 4:18:05 PM >> Subject: Re: [Observium] Changes made to Devices > Locations >> >> Hi Sonny, >> >> You can override the geolocation and return to the old behaviour by adding >> >> $config['location_menu_geocoded'] = FALSE; >> >> to your configuration file. I like it better too ;-) >> >> Tom > >Does that feature require a particular svn revision? I'm on 3934 and it >doesn't work for me. > >Or does it require something like rediscovery? > >Paul > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

Re: [Observium] FW: observium Digest, Vol 33, Issue 45
by Adam Armstrong 23 Apr '13

23 Apr '13

You are not our target market, then. Sam Munzani <smunzani(a)gmail.com> wrote: >> >> >> >>On 2013-04-22 15:32, Sam Munzani wrote: >>> 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. >> >>This is contra to the design ethos of Observium, thus there is no simple >>way to do this. >> >>Thanks, >>adam. > >While its a great concept, its not scalable. I have Qty 40 of the Cisco 48 >port switches and not all ports I care about. These are desktop ports and >I care to graph uplink ports only. Even if it does it efficiently, it is >junk data that I would never use. > >What would have been awesome is let Observium discover everything and let >administrators decide what they want to graph. > >Its sad that even though I like the tool, it doesn't fit me because of >this limitation(or so called feature). > >My 2 cents. > >Sam > > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

FW: observium Digest, Vol 33, Issue 45
by Sam Munzani 22 Apr '13

22 Apr '13

> > > >On 2013-04-22 15:32, Sam Munzani wrote: >> 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. > >This is contra to the design ethos of Observium, thus there is no simple >way to do this. > >Thanks, >adam. While its a great concept, its not scalable. I have Qty 40 of the Cisco 48 port switches and not all ports I care about. These are desktop ports and I care to graph uplink ports only. Even if it does it efficiently, it is junk data that I would never use. What would have been awesome is let Observium discover everything and let administrators decide what they want to graph. Its sad that even though I like the tool, it doesn't fit me because of this limitation(or so called feature). My 2 cents. Sam

2 1

Strange timezone behaviour in graphs
by Matt Hucker 22 Apr '13

22 Apr '13

Hi, I'm not sure what to make of this. When I try to enter custom time ranges in any of the traffic graphs, I get different results depending on which browser I'm using. Results are as follows. I'm in Brisbane (GMT +10). Mac OS X 10.6 Firefox: Observium always converts the time I enter (in local time) to GMT. Therefore my graphs are out by 10 hours. Safari: Won't accept any time info I enter. Always give me the last 24 hours. Chrom: Everything seems to work ok. Windows 7 Internet Explorer: Always gives me the last 24 hours. Same as Safari on OS X Chrome: Everything seems ok. Clicking any of the preset time periods, e.g 6 / 24 / 48 hours, always works ok regardless of which browser/os I'm using. Is this expected behaviour? Cheers, Matt.

1 0

New memory graphs
by David Brodbeck 22 Apr '13

22 Apr '13

Loving the new, more detailed Linux memory graphs. Much more useful now that I can see how much is actual memory use, and how much is cache that will be expunged as needed. -- David Brodbeck System Administrator, Linguistics University of Washington

1 0

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

fisheye
by Crozier, Doug 19 Apr '13

19 Apr '13

Is anyone else having problems getting to http://fisheye.observium.org/changelog/Observium?

3 2

Re: [Observium] polling interval
by Adam Armstrong 19 Apr '13

19 Apr '13

This is not possible with observium. Adam. J Z <jzthegeek(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

polling interval
by J Z 19 Apr '13

19 Apr '13

Long-time user and lurker. Many thanks to Adam and those who volunteer their time on this awesome project. I was wondering if there was a way to modify the polling interval (aside from modifying the crontab entry). I know that there was a lot of work that had to be done to decrease the polling interval from 5 to 1 minutes in Cacti, so I imagine it's not as simple as simply changing the crontab entry for Observium to monitor a switch's traffic utilization every 60 seconds. Has anyone successfully done this? Is there something simple I'm missing to get this to work? Many thanks!

1 0

Re: [Observium] APC UPS and remaining Runtime
by Adam Armstrong 19 Apr '13

19 Apr '13

Hi, We currently have no sensor type to capture this. It is on the list, but as with everything else, no time and no resources. Adam. Chris Blake <chrisrblake93(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

APC UPS and remaining Runtime
by Chris Blake 18 Apr '13

18 Apr '13

Hello, Not sure if I am doing this right (using the mailing list) so please don't kill me if I am. I currently have a APC UPS SMT2200RM2U, and I just recently added it to my Observium panel vi SNMP v2c. I see it logs everything from the current load to battery temp, but I am kind of surprised it does not log Battery Run Time Remaining. I checked in the latest APC powernet.mib file, and there is a function to call this. So, I updated the /opt/observium/mib/apc/powernet.mib to the latest version, but observium still does not log or show the remaining run time, which leads me to believe it is not coded into the script. Just wondering if this is a plan for the future, or am I doing everything wrong? Thanks, Chris B

1 0

Polling Rate on a 3750 Stack
by Michael Sweikata 18 Apr '13

18 Apr '13

Is anyone else having huge response times in their polling of a Cisco 3750 stack? I've increased the number of pollers I have to something close to 17, but my 3750s seem to take forever to respond (anywhere between 200 - 999.99+ seconds). It may be an issue on my 3750s, but my polling intervals on my devices is several hours. I have 2950s and 6509s that don't seem to have any issue responding in a short amount of time (<20 seconds).

6 11