Monitoring console
- Monitor frequency adaptable to every 1-60 minutes
- Monitoring locations/countries can be customized
- Schedule maintenance slots
- Time-out and performance thresholds can be defined
- Define redirection limit, HTTP compression, user-agent, etc.
- Organize monitors using folders and tags
Alerting triggers
- All triggers are fully configurable in console
- Absence of content in page or file
- Presence of content in page or file
- Content matching on strings
- Content matching on regular expressions
- Slow performance (in a step) in an script
- Transaction failure in a script
- Object Failures (in a step) in a script
- When Service is up again an alert can be sent
- When Service is down a reminder after ... minutes can be configured
- When service has been down for more than ... minutes, an alternative contact can be alerted
- All time-out errors are checked from a second location to prevent false positives
Alert configuration
- Alert windows can be set for all channels
- Alert windows can be set per script
- During Incidents Alerts can be switched off manually
- Alert contains Time Stamp, Name of Script, Error Type, Step in Error

Reporting
- Reporting can be configured in the console
- Statistics/reports per hour, day, week, month and year on availability and response times
- The tool creates reports that provide insight into recurrent performance and availability problems by time unit (day, week, month)
- On demand report generation must be possible; reports can be created at any time by users
- Create an export of the scripts that are used
- Reports can be exported to PDF
- Reports can be exported to Excel
- Reports can be sent via email
- Periodic (day, week, month) reports can be automatically sent via email
- Periodic (day, week, month) reports can be automatically stored in the console
- Reports are downloadable via API
- Data Cubes are downloadable via API
- Graphs are available in PNG
- Graphs are available as interactive Flash objects
- Raw data is available for 30 days
- Root cause analysis details are available 48 hours
- Root cause analysis details are kept available for a week (7 days) for error logs
- Statistical data is available for 4 months
Security
- Access to the console is protected by username and password
- HTTPS is available for console access
- Access to the API is protected by username and password
|
Protocols
- Web protocols: HTTP(S), including redirects, compression, user agents, etc.
- File transfer protocols: FTP(S), SFTP, TFTP, SCP
- Name service protocols: DNS, Domain
- Directory service protocols: LDAP(S)
- Email protocols: POP3, IMAP, SMTP
- Network level checks: ping, TCP connect
- Other protocols: SIP, XMPP
- User name/password authentication on all (applicable) protocols
- Client certificates authentication
- IPv6 support
- Full page support (via scripts)
- SSL certificate expiration checks
Functional tests (scripting)
- Multi-step functional and performance testing
- Support for JMeter recordings
- Forty script steps
- Scripts can be recorded with JMeter
- Script frequency can be set to 5-60 minutes
- Scripts can handle Internet pages like a standard web browser
Notifications
- Alert notifications can be configured in console
- Alerts can be sent via email
- Alerts can be sent in a text
- Alerts can be sent via RSS Feed
- Alerts can be forwarded to a web page (API)
- Work schedule can be defined per contact
- Contacts can be grouped
- Escalations can be defined in contact groups
- Reception of alerts is logged (where available)
Performance dashboard
- Dashboard is configurable in the console
- The tool has a dashboard in which historical availability and recent alerts are visible
- The aggregated results of the (test) scripts can be shown on the top level dashboard
- The dashboard contains near real time information with a view per day and hour of availability and drill down capability
- Show colours on the dashboard which are defined by configurable SLA input: (e.g. 100-99% = green, 98-99% = yellow, under 98% = red)
- The dashboard shows the availability figure of the day for each of the scripts
Root Cause Analysis
- The tool gives detailed insight in problems and incidents
- During an incident the tool shows the steps of the scripts that were (not) completed
- A screenshot is made after a monitor is triggered
- Traceroute of one or more stations after a monitor is triggered
- Raw HTML is available when an error occurs
- A DNS analysis is made after a monitor is triggered
- A domain analysis is made after a monitor is triggered
User management
- User Management can be configured in the console
- Extra users can be added which each have access to parts of the monitoring data
|