Web Performance Monitoring Metrics

We previously discussed 5 different types of web monitoring. Here is the list of important metrics that each of these services can provide for holistic web performance management.

Visitors Tracking

• Pages views
• Unique visitors
• New visitors
• Returned visitors
• Visitors distribution by countries and cities
• Browser statistics
• Max traffic
• OS statistics
• Referrers
• Entry pages
• Exit pages
• Time spent
• Conversion rate
• Most popular pages
• Common paths
• Search keywords

External Monitoring

• Response time from different external locations
• Uptime daily/monthly
• Average response time all location per URL
• MTTF (mean time to failure)
• MTTR (mean time to repair)
• Aggregated Uptime
• Incidents after working hours
• Average response time all web services
• Planned downtime
• Failures and notification

Internal Monitoring

• Server resource utilization (CPU, Memory, Network, HDD, Virtual Memory, Threads, Process)
• Total free disk space
• Number of alerts on exceeding system capacity thresholds
• Process resource utilization
• Response time local
• Process uptime
• Server uptime
• Uptime local

Online reputation Monitoring

• backlinks per SE
• indexes per SE
• position per keyword per SE
• social bookmarks
• references in blogs
• references in news
• page ranks

Transaction (application) Monitoring

• Failed transactions
• Coverage
• Total execution time
• Execution time per each step
• SLA figures (uptime)
• Page load breakdown
• Average execution per step

5 Monitors for Ultimate Business Performance: Part 5 Transactions Monitoring

5. Transactions (a.k.a. Application, Web Workflow, Functional) monitoring – monitors not only single web page but sequence of web screens and user actions. It allows checking functionally of web application logic and measure the performance of web transactions. A test script should be developed in order to perform such checks, either by automated recording of user actions or by writing the code manually. Monitis recently beta launched a transaction monitoring feature which allows to record, edit by hand, and debug test scripts. After recoding the script can be deployed on the server and then will be running on regular intervals. Users can see total execution time of script, but also can drill down to execution time per each step. In case of failure Monitis will send an alert. It also records screens which did not pass via checkpoints, thus allowing understanding the problem of failure later on. Finally it provides breakdown of load time per each component of the tested web pages.

Who should use it: business owners, webmasters, IT operations, QA and web developers.

Usage examples: a tool for regression tests of live production or pre-live development servers, functional monitoring to make sure main application flows are functioning, performance management and tuning.