You can estimate the size of client monitoring data to gauge its impact on network bandwidth and other resources. The number of counters depends on the number of clients, and on the number of endpoints, transports, and event queues in each client.
Procedure
For each application instance definition, determine the number of counters per client of that application instance. Combine information from the application instance definitions with information from the following table.
Client Monitoring Resource Usage
11 counters per client
3 counters per endpoint
2 counters per event queue
3 counters per transport (other than multicast transports)
9 counters per multicast transport (6 specific to multicast, in addition to the 3 counters common to all transports)
For each application instance definition, multiply the number of counters per client (as determined in the previous step) by the expected number of client instances.
Sum that number of counters over all the application instance definitions to obtain the enterprise total number of data samples generated in each sample interval.
When estimating bandwidth requirements, remember that each data sample travels between multiple components. Depending on the network architecture, the contents of a specific data sample may traverse the network several times, possibly across the same network segments or links. See
Data Flow of Monitoring Data and Log Messages.
Multiply the enterprise total by the number of samples you plan to retain in your monitoring data repository.
This product estimates the total volume of metric data.
