Joaquinl wrote:How much does it cost to monitor one transaction on 15-minute intervals for one month?
There are serveral separate activites that make up eValid-type "deep transaction monitoring" and to understand how this works here are the basics.
(1) Establishing the UseCase: What is to be monitored, for what, what are the thresholds for alarms and what is the email to which alarms are to be sent?
(2) Recording the script "from life": Based on the UseCase we record the basic script sequences. OR, you can record the script (so it becomes a UseCase itself).
(3) Enhancing the script for monitoring mode operation: This involves modifications of the script to account for timing (time bands) and also to solve any potential script playback de-synchronization commands. [Remember, you are running the script against an application that is going to behave variably -- that's why you're monitoring it! -- and you don't want your script to fail except when it is supposed to fail (when the application really is broken).
(4) Provisioning the monitoring agent: This involves setting up the scheduler and the appropriate reporting agent so that the outcomes of each run are saved locally and/or sent to the reporting engine.
(5) Provisioning the reporting engine: The reporting engine has to receive and properly process the data. If you are using our own reporting engine, eValidator, this is quite simple. But eValid monitoring agent outcomes can be sent to a wide variety of reporting engines.
Doing all of these for a single script on a 15-minute interval for a single month is probably not going to be a good estimate...because all of the setup work just described has to be amortized over too short a period. The normal agreement is for a year, with quarterly updates to the script.
Please contact for sales for specific price quotes.
eValid Monitoring Team