Landenc wrote:Can I get detailed timings from a monitoring test when eValid is imitating a mobile device browser?
The monitoring mode style of operation means, in effect, that there'll be no direct human user looking at eValid as it runs and there'll be nobody to look at an EventLog
or a TimingLog
What we have found is either to interface the eValid monitoring agent's output to a network monitoring system (our demonstration version of this uses the GWOS community edition and the NagVis interface). This works
well and is effective for most uses.
Detailed numerical value time analysis is often a requirement, and in that kind of case what we do is put SaveRecord
commands into the script to capture specific sub-test event timings (and byte counts) into a local text file. This kind of data is "spreadsheet" ready and from that you can do any kind of detailed statistical analysis you can imagine.
-eValid Monitoring Team