Understanding metrics
Metrics and data series
For each entity defined in TrueSight Capacity Optimization, various data series can be collected that contain useful metrics for capacity planning. Every data series is characterized as follows:
- Resource: The official name of the metric (for example, CPU_UTIL).
- Name: A short description of the resource (for example, a chart label titled CPU Utilization %).
- Subresource: The component of a resource to which a metric refers. The name of the resource includes the prefix BY. For example, the BYDISK_UTIL metric measures utilization by disk.
- Type: The metric type (for example, percentage or rate).
- Location: The position of the resource.
- Unit of measure: The metric's measurement unit (for example, bytes, MB, or number of events).
Configuration data
Systems and business drivers contain a set of configuration data - special type of metrics that either changes slowly over time or remains unchanged. Some examples of configuration data are:
- Core CPU frequency
- Database CPU count
- Database product version
- Hard disk size
- Installed memory
- OS version
Because configuration data changes slowly, the Data Warehouse stores only delta records for them. Tracking configuration data and changes is useful for performing what-if analyses, incident analyses, understanding the reasons behind some performance issues, and so on.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*