forum.e-valid.com

No, testing was done using the detailed log output setting for the
default event log, as it contained the most information. There are
certain "failure" conditions that we want to catch that won't necessary
register as a step error in eValid (ex. failure to download the
stylesheet for a page).

Is there information available for using the "custom log" format for
this?

Actually, the CustomLog is a grep-based subset of the EventLog: you specify
a set of strings in a file and eValid copies any line that has a string match
with any line in the EventLog into the CustomLog...

* eValid has the capability to create a custom subset of the regular
event log data, called a "custom log", by filtering the data with
a user-selected set of options or keywords/strings:

http://www.e-Valid.com/Products/Documen ... lters.html

Do you have defined steps? If so, then our convention (it is only that)
is to annotate them with ElapsedTime "Step NN -- message" type comnmads.

Will the executing target PC have PERL installed? If so then the
other scripts could be the basis of the integration into Zenoss...