- observium - lists.observium.org

Observium with Hyper-v
by Patrick Goldbach 06 May '13

06 May '13

Has anyone been able to have a hyper-v virtual as a device being monitored by Observium successfully capture the network traffic of the hyper-v virtual? -pg

1 0

Adding MIBs
by Gerry Armstrong 06 May '13

06 May '13

Hi Guys, I am new to Observium and so far have found it to be very interesting and would like to know if it is possible to extend the MIBs that are used to include Mitel equipment. I have the MIBs and have uploaded them to the MIB direectory but am not sure how/if I can include these in the discovery/polling so that I get all the info from our Mitel PBXes available via these MIBs. Regards, Gerry

2 3

Re: [Observium] VRF's on a Cisco 6500 series
by Adam Armstrong 06 May '13

06 May '13

The op is running sup2t, so likely quite different code if you have sup & RSP 720s. Adam. Sander Steffann <sander(a)steffann.nl> wrote: >Hi, > >> Better start complaining to Cisco then; read carfully what Adam is saying. >> >> If VRFs are discovered on 7k6 but not on 6k5, it's not Observium's fault, but buggy IOS... ;) > >Very true. I'll compare the 7600's and 6500's I'm working on for a customer as soon as I get the chance. Unfortunately I'll be traveling for the next three weeks, so don't hold your breath :-) > >Cheers, >Sander > >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

5 8

[094-19171955-0416] APC Nobreak Sensor :: Input :: Voltage = 0V without alerts
by noc.rodrigo.araujo＠itmnetworks.com.br 05 May '13

05 May '13

Hello, i have many APC nobreaks monitored by Observium. but, if the Sensor :: Input :: Voltage = 0V i not receive Alert. How i can receive Alerts if the nobreak not receive Voltage on Power Input ? Thanks, Rodrigo Araujo ITMNETWORKS Brazil

4 3

Re: [Observium] Kickstarter project.
by Adam Armstrong 04 May '13

04 May '13

Thanks :) Rachid Zarouali <rzarouali(a)gmail.com> wrote: >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Kickstarter project.
by Adam Armstrong 04 May '13

04 May '13

Hi All, As promised, we've launched a Kickstarter project to fund development of up/down & threshold alerting. http://www.kickstarter.com/projects/588464062/observium-alerting If you want it, vote with your wallets, guys! :) Thanks, adam.

10 11

Email Alerts
by Carlos Zurita 03 May '13

03 May '13

Hi, I'm test the tool, in this latest version works email alert, TK

2 1

Re: [Observium] Possible bug with whois?
by Adam Armstrong 03 May '13

03 May '13

Only if you disable selinux :D Laurens Vets <laurens(a)daemon.be> wrote: >Found the issue. We are running Observium on CentOS 6 (Yes, we followed >the RHEL documentation to the letter). The default selinux policy does >not allow whois be run from within Apache. After we fixed this, whois >worked. > >Is RHEL/CentOS still an officially supported OS for Observium? > >On 2013-05-02 20:20, Adam Armstrong wrote: >> I have no idea what's causing this. It works fine for me. >> >> It's the whois process getting all badly behaved, so it looks like >> it's their problem. Perhaps that particular version doesn't like >> being >> run from within PHP without a proper terminal? >> >> Of course, you don't tell us the versions of anything you're running >> at all, so I don't know why I'm even bothering... >> >> adam. >> >> On 2013-05-02 14:51, Laurens Vets wrote: >>> Hello list, >>> When Observium tries to do a whois of an RFC 1918 address, whois >>> goes >>> to 100% CPU and stays there... it doesn't seems to exit. I have to >>> manually kill the whois process. >>> Top output: >>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >>> 4480 apache 20 0 12716 1148 908 R 100.0 0.0 5:06.30 whois >>> Process output: >>> [root@box observium]# ps aux | grep whois >>> apache 4479 0.0 0.0 11332 1164 ? S 13:41 0:00 sh >>> -c >>> /usr/bin/whois 10.250.1.1 | grep -v \% >>> apache 4480 99.8 0.0 12716 1148 ? R 13:41 5:15 >>> /usr/bin/whois 10.250.1.1 >>> root 7325 0.0 0.0 103248 836 pts/1 S+ 13:46 0:00 >>> grep whois >>> [root@box observium]# >>> I suspect that either whois should either timeout or don't lookup >>> RFC >>> 1918 addresses (or multicast or loopback?). Or should I wait longer >>> then 5 minutes? >>> Kind regards, >>> Laurens >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

3 3

User Access Levels
by John Macleod 03 May '13

03 May '13

Is this documented anywhere or did I not look hard enough? Just looking to add a user with the same viewing abilities as an admin, but unable to make any changes. A level of 1 doesn't allow them to view anything at all. 8 more options to try I guess ;)

2 1

Possible bug with whois?
by Laurens Vets 03 May '13

03 May '13

Hello list, When Observium tries to do a whois of an RFC 1918 address, whois goes to 100% CPU and stays there... it doesn't seems to exit. I have to manually kill the whois process. Top output: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4480 apache 20 0 12716 1148 908 R 100.0 0.0 5:06.30 whois Process output: [root@box observium]# ps aux | grep whois apache 4479 0.0 0.0 11332 1164 ? S 13:41 0:00 sh -c /usr/bin/whois 10.250.1.1 | grep -v \% apache 4480 99.8 0.0 12716 1148 ? R 13:41 5:15 /usr/bin/whois 10.250.1.1 root 7325 0.0 0.0 103248 836 pts/1 S+ 13:46 0:00 grep whois [root@box observium]# I suspect that either whois should either timeout or don't lookup RFC 1918 addresses (or multicast or loopback?). Or should I wait longer then 5 minutes? Kind regards, Laurens

2 2