by monitoring » Tue Apr 07, 2009 4:24 pm
Most of the integrations that we have currently in our inventory
are PERL scripts. These PERL passages usually analyze an eValid
EventLog and extract data from it that is passed on to the network
monitoring system.
You're in luck because we do have those scripts for Nagios and we're
happy to send them to you on request.
In general, there are two forms of data reduction that are used most
often, and we'll discuss them separately.
In both cases, of course, the system reports failures and overtime
alarms or errors as "red screen" type events.
(1) Total Transaction Reporting
In this case the information you pass on to the reporting engine is
the set of command statistics (number with OK, or non-OK status),
the exit code of the run, the number of URLs visited, the total
bytes downloaded, and total playback time.
This is the data you need to know to make sure that the script
completed every step, and did so within the time limits set for it.
(2) Tiered Transaction Reporting
This form includes all of the above information but also adds in the
total time spent in each stage, or tier, of the playback.
A tier here could be one or several or many actual commands, but
generally involves all of the work needed for one type of operation.
For example, you might create tiers that measure login time, item
search time, shopping-card pickup time, checkout time (filling out
the forms), and then total time.
Here the data you see would be a multi-line chart that has each tier
(or section) of activity as a separate band.
Most customers like this tiered approach because it lets them see
which part of the test is running slower (or faster).
eValid Tech Support Team
