- observium - lists.observium.org

Re: [Observium] MySQL/Apache apps
by Ben Gatewood 23 Mar '15

23 Mar '15

Have you set the “Agent Port” section in your config? Ben On 16/03/2015 09:27, "Asensio Sánchez, Juan" <jasensios(a)indra.es> wrote: >Hi > >We have just installed Observium from SVN, added some hosts, and almost >everything seems to work fine. We have some MySQL servers, and followed >the instructions to get the graphs. Running observium_agent in the MySQL >server, I get the <<<mysql>>> section. Doing telnet to the MySQL server >from the Observium server, to the agent port, I get the same section, >but I don't get any data in the device page. Any advice? The same >happens with the Apache servers. > >Regards. > >Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, >contiene información de carácter confidencial exclusivamente dirigida a >su destinatario o destinatarios. Si no es vd. el destinatario indicado, >queda notificado que la lectura, utilización, divulgación y/o copia sin >autorización está prohibida en virtud de la legislación vigente. En el >caso de haber recibido este correo electrónico por error, se ruega >notificar inmediatamente esta circunstancia mediante reenvío a la >dirección electrónica del remitente. >Evite imprimir este mensaje si no es estrictamente necesario. > >This email and any file attached to it (when applicable) contain(s) >confidential information that is exclusively addressed to its >recipient(s). If you are not the indicated recipient, you are informed >that reading, using, disseminating and/or copying it without >authorisation is forbidden in accordance with the legislation in effect. >If you have received this email by mistake, please immediately notify the >sender of the situation by resending it to their email address. >Avoid printing this message if it is not absolutely necessary. >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

3 2

Re: [Observium] alert after 2 checks
by Tom Laermans 23 Mar '15

23 Mar '15

Yes. Set delay to 2 :) On Mar 23, 2015 6:07 PM, Simon Smith <simonsmith5521(a)gmail.com> wrote: > > Hi All, > > Im just wondering if this is possible, it may not be, or I just may not know how to do it? > > Currently i have a check thats says if bandwidth on a port more than 75%, then alert me… > > BUT i want the alert to only send me an email if after say 15mins its still over 75% ? > > i currently check our kit every 5 mins, so it work out after 3 checks > > Is this possible? > > regards > > Simon - Hestor Ltd > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

alert after 2 checks
by Simon Smith 23 Mar '15

23 Mar '15

Hi All, Im just wondering if this is possible, it may not be, or I just may not know how to do it? Currently i have a check thats says if bandwidth on a port more than 75%, then alert me… BUT i want the alert to only send me an email if after say 15mins its still over 75% ? i currently check our kit every 5 mins, so it work out after 3 checks Is this possible? regards Simon - Hestor Ltd

2 1

Duplicate device neighbour entries
by Chard, Alex (RET-SYD) 23 Mar '15

23 Mar '15

HI All, Just wondering is anyone has seen this happening before. We have switches that run LLDP and CDP. On most switches, Observium correctly determines that the neighbour entries for each protocol are identical and ignores the second one from LLDP. However on one switch, it's decided that it represents a separate connection (see attachment) I suspect it has to do with the differing port ID, but Observium seems to be able to reconcile that on other switches. Any ideas? Thanks, Alex This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this e-mail. We cannot accept liability for any loss or damage caused by software viruses.

1 1

Re: [Observium] Critical alert not matching alerts checker
by Tom Laermans 23 Mar '15

23 Mar '15

Quick reply from my cellphone, you need an alert checker for entity type status instead of sensor since a few weeks... Tom On Mar 22, 2015 7:55 PM, Robert Williams <Robert(a)CustodianDC.com> wrote: > > Hi All, > > > > I have a device a Cisco 2960G with a failed internal PSU that has switched to it’s backup RPS supply. Observium is correctly identifying this as ‘critical’ under the Status Indicators for the device in question (image below): > > > > > > > > There is a “Hardware Fault” event I have created which /should/ have matched this, I believe: > > > > > > (I’ve added the match for value = critical as a test, it wasn’t there originally) > > > > This alert checker correctly matches a who load of devices and status checkers on many devices (1691 in total, all green): > > > > > > However, for this particular type of sensor, it does not see any sensors which match the “Hardware Fault” checker. As you can see, I have already removed all the “Device Match” and “Entity Match” criteria from the checker itself to rule that out. So essentially this checker is matching every type of sensor that there is (except, obviously, the one which I want it to). > > > > When I click the link on the graph for “Sw1, PS1 Critical, RPS Normal” sensor I get this URL http://observium-server/device/device=343/tab=health/metric=status/ which may be of use in helping diagnose this. > > > > After doing some more checking, I’ve found that it is not matching any other kind of sensor with a similar class, for example it does not match the WS-CAC-4000W-IN power supplies in any of the Cat6k chassis either. > > > > In fact, I think it’s actually failing to match sensors which have ‘normal’ and ‘critical’ type statuses, instead of ‘true’ and ‘false’ > > > > So the following sensors highlighted in yellow are also being missed from matching in this generic alerting config: > > > > > > So I believe it’s a wider issue and not just related to this one device. > > > > Can someone confirm what I’m doing wrong and/or maybe check to see if your alerting configurations can match sensors which have an OK state of ‘normal’ instead of ‘true’? > > > > Cheers! > > Robert Williams > Custodian Data Centre > Email: Robert(a)CustodianDC.com > http://www.CustodianDC.com

2 4

Map and Neighbours
by Dudu 23 Mar '15

23 Mar '15

Hi All, For some reason I don’t have the Neighbours and Map tabs under the ports page. It's probably something that I have change but I'm unable to find it. Also the mysql link table is empty. Any idea? Thanks David

1 1

Critical alert not matching alerts checker
by Robert Williams 22 Mar '15

22 Mar '15

Hi All, I have a device a Cisco 2960G with a failed internal PSU that has switched to it’s backup RPS supply. Observium is correctly identifying this as ‘critical’ under the Status Indicators for the device in question (image below): [cid:image001.png@01D064D0.36501EE0] There is a “Hardware Fault” event I have created which /should/ have matched this, I believe: [cid:image002.png@01D064D0.36501EE0] (I’ve added the match for value = critical as a test, it wasn’t there originally) This alert checker correctly matches a who load of devices and status checkers on many devices (1691 in total, all green): [cid:image003.png@01D064D0.36501EE0] However, for this particular type of sensor, it does not see any sensors which match the “Hardware Fault” checker. As you can see, I have already removed all the “Device Match” and “Entity Match” criteria from the checker itself to rule that out. So essentially this checker is matching every type of sensor that there is (except, obviously, the one which I want it to). When I click the link on the graph for “Sw1, PS1 Critical, RPS Normal” sensor I get this URL http://observium-server/device/device=343/tab=health/metric=status/ which may be of use in helping diagnose this. After doing some more checking, I’ve found that it is not matching any other kind of sensor with a similar class, for example it does not match the WS-CAC-4000W-IN power supplies in any of the Cat6k chassis either. In fact, I think it’s actually failing to match sensors which have ‘normal’ and ‘critical’ type statuses, instead of ‘true’ and ‘false’ So the following sensors highlighted in yellow are also being missed from matching in this generic alerting config: [cid:image004.png@01D064D1.B26D89D0] So I believe it’s a wider issue and not just related to this one device. Can someone confirm what I’m doing wrong and/or maybe check to see if your alerting configurations can match sensors which have an OK state of ‘normal’ instead of ‘true’? Cheers! Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

1 0

Down ports but can't see them
by Chard, Alex (RET-SYD) 20 Mar '15

20 Mar '15

Hi All, Got an interesting issue... Observium's dashboard shows 2 down ports [cid:image001.png@01D06344.0CB21DF0] But clicking on "2 down" takes me to a screen that shows no down ports: [cid:image002.png@01D06344.0CB21DF0] If I have any more than 2 down ports, they are displayed correctly. Any idea how I can identify the offending ports? Thanks, Alex This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this e-mail. We cannot accept liability for any loss or damage caused by software viruses.

1 0

tons of rrd zombie processes + solution
by Gerwin Krist 19 Mar '15

19 Mar '15

Hi, FYI on PHP 5.5 we saw a lot of defunt rrdtool proceeses (1 for every image created in the browser). If you see this there are a couple of fixes/work-around: 1. Fix it in observium, open ./includes/rrdtool.inc.php and change *function rrdtool_pipe_close(&$rrd_process, &$rrd_pipes)* to *function rrdtool_pipe_close($rrd_process, &$rrd_pipes)* 2. downgrade to PHP 5.4 Seems to be caused by https://bugs.php.net/bug.php?id=69014 Regards, Gerwin Krist

2 1

Purchase support
by Dudu 19 Mar '15

19 Mar '15

Hi All. How can i buy support? I would like to finance and improve the product. Thanks David Sent from my Samsung Galaxy smartphone.

1 0