This article is part of a series, beginning with Analytics Application - Concepts and Metrics Explained
The Analytics Application included in Services Director can provide reports on the most common events tracked though the application through the Top Events tab:
Top Events: Top 5 URLs:
- The five vServer URLs most often requested in the selected part of the dataset.
For the purposes of this chart, vServer URL is defined as a combination of URL and the vServer that handles it as <vServer>:<URL>. - The number of requests directed towards these vServer URLs.
- The average request duration for requests for each vServer URL.
Each bar on the graph represents a different vServer URL. The length of each bar represent the number of requests directed to the vServer URL, while the color of the bar represents the average duration of these requests. The metrics for this graph are derived as follows:
- Combine the vServer name and request URL into a vServer URL (<vServer>:<URL>)
- For all request-based records, calculate the count and the average request duration, both split by vServer URL.
- Make a descending sort of the result by request count, and remove any results below the fifth row.
Top Events: Top 5 Traffic IPs
The Top 5 TIPs chart on the Top Events tab shows:
- The five front-end Traffic IPs that handled the most connections and requests in the selected part of the dataset.
- The number of requests and connections directed towards each of them.
- The average combined duration of the requests and connections.
Each bar on the graph represents a different front-end Traffic IP. The length of each bar represents the number of requests and connections handled by the front-end Traffic IP, while the color of the bar represents the average combined duration of these requests and connections. The metrics for the graph are derived as follows:
- For all requests and connection records, calculate the count and average duration, both split by Traffic IP.
The duration for request based transaction records is calculated as (timeline.crse - timeline crqs), while for connection based transaction records it is the value of the 'duration' field. - Make a descending sort of the result by request/connection count, and remove any results below the fifth row.
Top Events: Top 5 Referrers
- The five HTTP referrers that originated the most requests in the selected part of the dataset.
- The number of requests with each of those referrers.
- The average duration of those requests.
Each bar on the graph represents a different HTTP referrer. The length of each bar represents the number of requests originated by that referrer, while the color of the bar represents the average request duration. The metrics for the graph are derived as follows:
- For all request-based records, calculate the count and the average request duration, both split by HTTP referrer.
- Make a descending sort of the result by request count, and remove any results below the fifth row.
Top Events: Top 5 Pools
The Top 5 Pools chart on the Top Events tab shows:
- The five pools that that handled the most requests and connections in the selected part of the dataset.
- The number of requests and connections handled by those pools.
- The combined average duration of the requests and connections.
Each bar on the graph represents a different pool. The length of each bar represents the number of requests and connections handled by the pool, while the color of the bar represents the average combined duration of the requests and connections.
The metrics for the graph are derived as follows:
- For all requests and connection records, calculate the count and average duration, both split by pool.
- Make a descending sort of the result by request/connection count, and remove any results below the fifth row.
HTTP Response Code Charts
The Analytics Application also offers a way to chart HTTP Response codes, which is presented as a Comparative Analysis view in the article Interpreting Horseshoe and Timeline Charts.
The HTTP Response Code chart shows the HTTP response code distribution for the selected part of the dataset. The distribution is broken down by pool (by default), and then by the response code group (such that HTTP response codes 200, 201 belong to response code group "2XX", while 400, 403, 404 belong to the group "4XX", and so on. Note that if a split has been selected for the primary chart, then that same split is used for the HTTP Response Code chart in place of the pool split.
Each column in the graph represents a different pool (or value from the primary chart split), with the overall height of the column representing the total number of requests handled, and the height of subdivisions within that column showing the distribution of the response code groups. The metrics for this graph are derived as follows:
- Convert the HTTP response code into an HTTP response code group
- Count all request-based records, split by HTTP response code group and pool name
This article is part of a series, beginning with Analytics Application - Concepts and Metrics Explained
Prev: Interpreting Horseshoe and Timeline Charts
Next: Using the Component Filter to Refine Queries
