eValid -- The WebSite Quality Suite
Functional Testing and Validation,
Web Page Timing/Tuning,
Quality Assurance, and Performance Monitoring.
eValidator -- Typical Monitoring/Reporting Architecture
The diagram below shows all of the components
of a typical eValid-based monitoring architecture
that relies on status reporting via email and via the
eValidator Portal of your choosing.
Typical Monitoring/Reporting Architecture
Click to Enlarge Diagram [New Window]
Here are short explanations of the items in the diagram, from left to right.
- Web Apps:
The web applications being monitored.
- Local Web Server:
Supports the web applications being monitored are served from this machine.
- evalid Agent PC:
This is where the machine
on which the eValid monitoring agent plays back the monitoring script.
This machine may be co-located with the local web server, or
could be a virtual machine on the same hardware, or could be
a machine that communicates to the application over the web.
- Email Alerts, Warnings:
Tests that throw a warning or alert flag
send messages to management via email.
The information collected by eValid is sent
over the local LAN or over the web (via FTP)
to the eValidator Portal.
This data transfer software is part of the eValid
agent support package.
- eValidator Portal:
This monitoring data repository is shere
reports from multiple monitoring agents are archived
and made accessible to authorized users.
- eValidator Reports:
Reporting from eValidator showing time-band details to user.
The reporting done is based on special markers in the eValid monitoring
Typical reports show hourly, weekly, monthly, and yearly averages of
response time data.
- User Login:
Users may log in to the eValidator system from any location using
any web browser.
- Manage Account:
The account manager can control the
reporting intervals and thresholds and other data display criteria.