The sa_case part still had to be answered :-)
Example:
<sa_select_case status>
<sa_case UP>
<b><sa_hostname> (<sa_checkdescription>)</b>
<sa_case DOWN>
<I><sa_hostname> (<sa_checkdescription>)</I>
</sa_select_case>
The big advantage of using the sa_select of sa_if is that with the sa_case
the resulting output can be over more lines. With sa_if the start and stop
of the tag need to be on the same line.
HOWEVER currently the sa_select ONLY works with STATUS as var. We will
extend that in the future.
Hope this helps.
Dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Rob Morgan
Sent: Friday, March 18, 2005 7:46 PM
To: [email protected]
Subject: [SA-list] HTML Output
Hi Everyone,
I believe I have detected a bug using the HTML tag SAIF when checking
the variable sa_check when its value is EXTERNAL. Even though I am
using plenty of COM External checks the condition is never detected.
However, it does correctly detect for others such as SERVICE, etc..
There is a documentation error for use of sa_check_response when using
under <SAIF>. The operator CON works but NC0 is mispelled. It should
be spelled with the letter 'O' not the number zero.
Can you provide some further explanation for the use of <sa_select_case
STATUS> and <sa_case>? I don't understand how this is used. 'STATUS',
is this a variable, the actual value, some other special word? Which
tag encloses which <sa_select_case> or <sa_case>? The documentation
shows <sa_select_case STATUS> with a closing tag, but not one for
<sa_case>. Is this true? --- It would be useful if a Case-like
statement could be used within the report body and not just in the
headers and footers. I do use SAIF for conditional processing, but
using CASE would make it easier when there are many conditions to check
for. Maybe this could be a future enhancement.
Also, can SAIF be changed to intelligently recognize the numeric
response given by such tags as <sa_nr_up>, <sa_nr_down>, etc., so that
conditional formatting can be done based on counts? I've tried and
can't get it working. How about adding <sa_checkdescription> and
<sa_threshold> to the list of variables that SAIF can check against,
including the use of the operators CON and NCO with each?
Could the Last Check Time for a particular test be added as an output
variable option for HTML? This is useful when cycles are set to skip at
such-and-such intervals.
Thanks,
Rob Morgan
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
