Modifying the number of sampled requests (to lower your Agent overhead)


To lower your BMC Application Diagnostics Agent overhead, modify the number of sampled requests. Sampled requests will be used to calculate statistics but will not be persisted, even if they contain latency/error breaches.

Tagged requests, such as requests that come from BMC TM ART, are persisted, even during high system load. Tagged requests are never sampled out.

The BMC Application Diagnostics Agent reads header types from the Agent policy, and for each entry point, regardless of sampling, gets the HTTP headers and their values.

If the header exists, the BMC Application Diagnostics Agent will persist the request, and the BMC Application Diagnostics Collector will add the request to the database.


The percentage of total requests that will be sampled (i.e. monitored) by the agent.
Allowed values: 0-100 inclusive.
Default is 50
sampling.rate=50

Related topics

Creating-and-editing-an-Agent-policy-file
Tagging
Applying-a-policy-to-a-BMC-Application-Diagnostics-Agent
Setting-a-default-Agent-policy

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Application Diagnostics 1.3