Hi David,
The problem is that the Alarm backend only allows you to create a single
event type from a status change. Therefore, although you get the ok /
degraded text through to the Event, it will always be raised at the same
severity, which I suspect is not what you want.
I had a similar issue some time ago where I was monitoring an OID which h=
ad
some concept of the severity of the alarm, and provided multiple states,
rather than just up or down, and wanted to raise an alarm and event relev=
ent
to this severity. In order to do this, I wrote the multi_alarm backend,
which will take "|" separated descriptors which will translate the poller
outputs (ok, down, degraded etc) into the associated Event IDs (defined =
in
the JFFNMS database). Therefore when the poller returns "down", it will
raise one (Critical) event, when it returns "degraded" it can generate
another (say Minor).
See my mail in the archive at
http://www.mail-archive.com/jffnms-users@...>
tml,
which describes the setup, and has the files required. Note that you wil=
l
have to pipe the SQL file through MYSQL, and replace the have_other_alarm=
()
function in /opt/jffnms/lib/api.events.inc.php with that included in the
"function_have_other_alarm.php" file. The multi_alarm.php file can be
dropped into the engine/backend directory as it stands. I would strongly
recommend backing up your database and files first!!
(BTW, Javier, I haven't forgotten about submitting the interface types wh=
ich
I was working on - will get those through soon).
Hope this helps.
Regards,
Craig
> ----- Original Message -----=20
> From: "LIMA David" <DLIMA@...>
> To: "Javier Szyszlican" <javier@...>
> Cc: <jffnms-users@...>
> Sent: Tuesday, August 02, 2005 2:06 PM
> Subject: RE : [jffnms-users] Generic snmp_status and
> temperature_aggreagation
>
>
>
> Hi Javier
>
>
> > snmp_status allows you to put more than 2 states. The first that matc=
hes
> will
> > be returned, and if no match is found, it will return "down" (that is
hard
> > coded).
>
>
> So if for example I create this =3D=3D>
> .1.3.6.1.4.1.232.6.2.6.7.1.9.<chassis>.<fanindex>,2=3Dup|1=3Dother|3=3D=
degraded
>
> How do I manage the 1 or 3 alarm state? do I have to add another alarm
type,
> because I want to know when my fan is in degraded mode (not down or up)
>
>
> 2- temperature_aggregation
>
> My discovery script is good because I pass the interface name to the
table.
> When I look at other aggregration graphs (Compaq) it's the same thing, =
the
> hostname and short-client are displayed in front of each rrdtool line b=
ut
> not the interface name (if you have 2 temp for the same host you can't
find
> out which line if for which sensor)
>
> _______________
> David LIMA
> Professional Services
> http://www.scc.com
>
>
>
>
> -----Message d'origine-----
> De : jffnms-users-admin@...
> [mailto:jffnms-users-admin@...] De la part de Javier
> Szyszlican
> Envoy=E9 : dimanche 31 juillet 2005 17:00
> Cc : jffnms-users@...
> Objet : Re: [jffnms-users] Generic snmp_status and
temperature_aggreagation
>
> Hi David,
>
> >
> > The problem is the same with Compaq temperature or fan interface type=
,
> JFFNMS is
> > sometime reporting down state but when we look at the Compaq Mib the
> > fans can be in other(1) ok(2) degraded(3) or failed(4) mode. When i
look
> at the logs I saw that Other state happens some times (I have less down
> events when I put this in the poller =3D=3D>
> .1.3.6.1.4.1.232.6.2.6.7.1.9.<chassis>.<fanindex>,2=3Dup|1=3Dother)
> > Perhaps we can extend the snmp_status to manage 3 or 4 states ?
>
> snmp_status allows you to put more than 2 states. The first that matche=
s
> will be
> returned, and if no match is found, it will return "down" (that is
> hard-coded).
>
> >
> > 2- temperature_aggregation
> >
> > The temperature graph is well shown but I can't see the Interface
> > Name front of each RRD line on the aggregation graph (only host name
and
> > zone shortname + RRD data: Average Max and Min). Do I miss somethin=
g
in
> > the Interface declaration ?
> >
>
> The interface name is taken from the "interface" field in the interface=
s
> table,
> you should check if the name is correctly set there, that is set by the
> discovery script.
>
> Javier
>
> --=20
> =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D
> Javier Szyszlican, Project Leader, JFFNMS
> javier@...
>
> I hope JFFNMS or I were helpful to you, if you
> can, please donate at http://jffnms.org/donate
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl=
ick
> _______________________________________________
> jffnms-users mailing list
> jffnms-users@...
> https://lists.sourceforge.net/lists/listinfo/jffnms-users
>
>
> -----------------------------------------------------------------------=
---
--
> --------------
>
> Ce message contient des informations dont le contenu est susceptible
d'=EAtre
> confidentiel.
> Il est destin=E9 au(x) destinataire(s) indiqu=E9(s) exclusivement.
>
> A moins que vous ne fassiez partie de la liste des destinataires, ou qu=
e
> vous soyez
> habilit=E9 =E0 recevoir le mail =E0 leur place, il vous est interdit de=
le
copier,
> de l'utiliser
> ou de d=E9voiler son contenu =E0 un tiers.
>
> Si vous avez re=E7u cet email par erreur, merci de prendre contact avec
> l'=E9metteur.
>
> Les opinions exprim=E9es dans cet e-mail sont celles de l'=E9metteur et=
ne
> refl=E8tent pas
> n=E9cessairement celles de l'entreprise.
>
> Ce e-mail peut contenir des pi=E8ces jointes dont certaines pourraient
> contenir des virus
> qui pourraient endommager votre syst=E8me informatique.
>
> La compagnie a pris toutes dispositions afin de minimiser ce risque et
> d=E9cline toute
> responsabilit=E9 pour toute perte ou dommage r=E9sultant directement ou
> indirectement de
> l'utilisation de cet email ou de son contenu.
>
> Il vous appartient d'effectuer vos propres contr=F4les anti-virus avant
> d'ouvrir
> la ou les pi=E8ces jointes.
> -----------------------------------------------------------------------=
---
--
> --------------
>
>
>
|