Number of similar requests
This topic explains how to configure the Application Diagnostics Agents to reduce the collection of similar requests.
Each server request instance is counted and measured for latency violations and errors, and represented by general metrics. However, only certain server request instances are monitored with the call tree for extended viewing.
For a server request to be monitored, the request must have following conditions:
- Included in the sampling mechanism
- Performance violation (latency), availability errors, or exceptions
- Detectable reference in the HTTP header (meaning that another BMC product has requested monitoring)
The performance and availability rates must be closely watched and should represent a service level percentage for the product.
The following table lists the parameters in the Agent Policy file that are used to control the number of similar requests it collects.
Parameters that control the number of similar requests
Parameter | Default value | Description |
|---|---|---|
persisting.single.worst.sla.breach. server.request.timeframe | 300000 ms (5 minutes) | Time, in milliseconds, in which only the worst SLA breaching requests are persisted |
persisting.error.server.requests. timeframe | 300000 ms (5 minutes) | Time, in milliseconds, in which error requests are buffered |
persisting.max.num.unique.errors.per. timeframe | 3 | Number of different error types that are sent in the time that is specified in the persisting.error.server.requests.timeframe parameter |
recording.regulator.staticThreshold. threshold | 2000 ms (2 seconds) | Global static threshold, in milliseconds, used for all entry points |
Changing these parameters can result in the BMC Application Diagnostics Agent storing more incidents of the same erroneous request.
The configuration restricts the number of similar errors in the following ways:
- No more than the number specified in the persisting.max.num.unique.errors.per.timeframe of different error requests are sent to the Application Diagnostics Collector in the specified time.
- A specific error request is not sent more than once to the Diagnostics Collector in the specified time.
- An error request is sent to the Diagnostics Collector only if it occurred in the previous time.
- If more than persisting.max.num.unique.errors.per.timeframe error types occur concurrently for a while, they are sent to the Collector in a round-robin fashion, so that all error types are represented, without violating other restrictions in these parameters.
Related topic
Modifying-an-Agent-policy-file