- observium - lists.observium.org

Power Meter MIB
by chott＠praha1.net 25 Nov '14

25 Nov '14

Hello, i have I have Power Meter HWg-PWR - http://www.hw-group.com/products/HWg-PWR/hwg-pwr25_M-bus_gateway_en.html Is there some future implementation? Tomas

2 3

CE 0.14.11.6000
by Dan Ratzlaff 25 Nov '14

25 Nov '14

Thanks for the new version! My RADLAN and BCM PowerConnect switches show up nicely now. I recently picked up a few Cisco Small Business switches, but Observium wasn't detecting them correctly. After some digging, I found I only needed to add their sysObjectID's to the definition file: diff --git includes/definitions/os.inc.php includes/definitions/os.inc.php index c54d476..135f3ae 100644 --- includes/definitions/os.inc.php +++ includes/definitions/os.inc.php @@ -714,6 +714,8 @@ $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.81."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.82."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.83."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.85."; +$config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.87."; // SF200-48 +$config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.88."; // SG200-50 $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.89."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.11.82."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.3955."; Thanks! -- Dan

5 5

Mako
by Tom Henderson 24 Nov '14

24 Nov '14

Has anyone used any of the Mako appliances (http://www.makonetworks.com/) with observium? They have their own management/monitoring platform but wondering if I'll be able to also add them to our observium server. We're looking at the 6500 model. Cheers Tom Henderson IT Manager | Pack & Company | 027 461 4403 | 09 929 2750 | tom(a)pack.co.nz -- ---------------------------------------------------------------------------If you are not the intended recipient of this email, you must not disclose, copy, or distribute any information contained in or attached to it, or take any action/inaction based on it. Please contact us immediately, and delete this email from your system. Any views or opinions presented in this email are solely those of the author and not of Pack & Company (NZ) Limited (the "Company"), however any intellectual property contained in or attached to this email is the property of the Company. Thank you.

2 1

idrac
by Robert Hatch 24 Nov '14

24 Nov '14

Dear all, Has anyone had any success in using observium with idracs? The auto discover doesn't appear to find any useful sensors other than the physical nic of the idrac itself. Has anyone else worked on support for idracs? All the best rob

5 17

Interface Parsing
by Robert Hatch 24 Nov '14

24 Nov '14

Dear all, Just wondering if there was an appetite out there for expanding the interface labelling feature of observium. The existing description parsing (http://www.observium.org/wiki/Interface_Description_Parsing) is pretty useful but also a bit limiting at times, as it seems more useful when labelling layer 3 services and less so for layer 2. Just a few general comments: * For us the pseudowires tab does not seem to auto populate (we use a variety of juniper, brocade and extreme switches and routers), just wondering if I have missed something here... * This aside there are more frequent occasions where we are providing VPLS services for a client and it would be nice if it were possible to label an interface as both a customer and a P2P link for example and then have these separately broken down in observium itself * There are also occasions where it would extremely useful to label backhaul circuits such as dark fibre and waves. Currently the only option for this is to label things as core but that page becomes so big it is not that useful unless you know what you are after (and then you would just go straight to the interface). Something like BACKHAUL: , PROVIDER:, END (A/B etc.) would be immensely useful and time saving. * The other issue we have that I don't have a simple answer for is the unhelpful aggregation of customer switch ports (quite often both ends of a P2P) and their layer 3 router ports. Could we start by having a separate aggregate graph for each circuit reference for each specific client. Maybe if END A and B are specified then the graph could demonstrate that these are actually different ends of the same link? What do people think? BW rob

3 3

New Community Edition
by Adam Armstrong 24 Nov '14

24 Nov '14

Hi All, We've released a new Observium Community Edition, version 0.14.11, based on SVN revision 6000. There've been over 770 new commits since the previous release. http://www.observium.org/observium-community-0.14.11.tar.gz http://www.observium.org/wiki/Upgrading#Upgrade_to_latest_Major_release http://www.observium.org/wiki/Changelog (will be updated later!) adam.

17 31

Observium Location Naming
by Gary Tang 24 Nov '14

24 Nov '14

Is there some kind of convention as to how to set the sysLocation snmpd parameters? I am currently having some trouble finding the right naming for OVH BHS. So far none of the following work. OVH, Montregie, Quebec OVH, Beauharnois, Quebec OVH, Beauharnois, Montregie OVH, Beauharnois-Salaberry, Montregie -- Gary Tang Sent with Airmail

4 3

Paid support
by Gavin Henry 24 Nov '14

24 Nov '14

Hi all, I can see some of the support options on the main website, but not way to purchase or get in touch? -- Kind Regards, Gavin Henry. http://www.surevoip.co.uk

7 8

Multiple SNMP Queries
by Lane Eckley 23 Nov '14

23 Nov '14

Hi Guys, On a limited number of CentOS & Ubuntu machines we are monitoring with Observium we are seeing dozens of SNMP queries from Observium in a very short window (10-20 seconds). Snip of the logs from /var/logs/messages Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:55776->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] Nov 21 14:43:52 hostname snmpd[22648]: Connection from UDP: [xxx.xxx.xxx.xxx]:37575->[xxx.xxx.xxx.xxx] We are trying to understand why Observium would be sending so many queries back to back as well as why we are seeing this on some machines, but not others. Thanks! -Lane

3 2

hddtemp on CE 0.14.4.5
by deeepdish 23 Nov '14

23 Nov '14

Hello. Great product. Looking forward to evaluating the subscription version after I get a minimum base operational using the CE edition. I have an issue around viewing HDD TEMP graphs driven by data extracted from the UNIX agent and hddtemp script. I can confirm output when auditing output of: telnet (hostname) 36602 or ./poller.php -h (hostname) -d I can also confirm temp. sensor driven graphs do come up for other hosts when using SNMP lmsensors, however not for unix-agent / hddtemp data sources. Can someone point me in the right direction? Thank you.

3 2