Two Questions: Capacity and Timing
![Post Post](./styles/Gray-Chrome-Blue/imageset/icon_topic_latest.gif)
For eValid in "monitoring mode" [as you describe it, but it seems to be just ordinary functional testing, but anyway...] I have two questions:
(1) What is a practical number of simultaneous eValid copies doing monitoring and what are the limitations that are imposed there?
(2) If I want to create a report in my monitoring system (I'm using Nagios) that shows bands of activity from test to test, how do I do it? Is there some trick inside the eValid script that makes this easy?
Ozzie the Wizzard
(1) What is a practical number of simultaneous eValid copies doing monitoring and what are the limitations that are imposed there?
(2) If I want to create a report in my monitoring system (I'm using Nagios) that shows bands of activity from test to test, how do I do it? Is there some trick inside the eValid script that makes this easy?
Ozzie the Wizzard