Re: [Bigsister-devel] How to include html tags?
Brought to you by:
aeby
|
From: Thomas A. <ae...@gr...> - 2006-07-11 07:46:16
|
Hello,
On Mon, 2006-07-10 at 17:24 -0500, Hern=C3=A1ndez L=C3=B3pez Carlos wrote=
:
> I have developed a module for monitoring sybase databases. It works
> fine,
Congrats! :-)
> but I would like to include some html tags in order to speed up the
> search of information as
[...]
> set text =3D=E2=80=9D<A HREF=3D\=E2=80=9D#${database}\=E2=80=9D> =
${label} </A>=E2=80=9D;
>=20
> status red ( ${status} =3D=3D 2) "&red" ${text} ;
Ok, I do not want this to work. Why? Status texts are not only appearing
on the status page, but are also used e.g. for alarming. Allowing what
you try to do would imply (besides other implications):
- every alarming script had to include a HTML parser
- there were information in the status texts that are useless
for those not reading them via the status page
If I understand well, in your case the "comment html" sections are
rather lengthy and it's not easy to find the section corresponding to
a bad status. I haven't got an ideal solution for this, but might it
help to add a contents section at the beginning of your html comment?
I assume this should be possible via a "pernode report" such as
pernode report {
comment html "<h3>databases</h3> ..."
}
"pernode" methods are usually executed before the first instance method
of the same host and name is executed, so html comments of a "pernode
report" should appear before those of a normal "pernode".
Of course, you have to assemble the entries for each database, either by
using a "for" or by storing them in a variable in the "monitor" or
"discover" method for later output by "pernode report".
Is this an acceptable approach?
Best regards,
Tom
--=20
-------------------------------------------------------------------------=
---
Thomas Aeby, Kirchweg 52, 1735 Giffers, Switzerland, Tel: (+41)264180040
Internet: ae...@gr... PGP public key available
-------------------------------------------------------------------------=
---
|