kristian wrote:Which databases and which monitoring environments can eValid fit into?
The quick answer, and we don't mean to be flip, is "all of them."
In monitoring mode the Windows scheduler invokes eValid via a batch (command line) interface, and eValid produces, as a byproduct of the test playback, a set of log files and possibly a set of in-play generated records (we call them SaveRecord files, because the
SaveRecord command is the one used to produce them).
As you may know, the eValid script and all of the standard eValid event log files are all simple to use, easy to handle, "flat files" -- simple text files.
All of that said, then, the job of interfacing eValid to
any reporting environment is easy, easy, easy. We know that eValid has been integrated into Groundwork, Nagios, Zenoss, Hyperic, CA/Oblicore and a varity of others as well.
eValid Support