Understand metric quotas and pools
Metric quotas assign specific percentages of your total persisted writes limit to pools of metrics. A pool might translate to teams or other logical groupings within your organization.
Use metric quotas to give each pool a specific quota of your total persisted writes license, expressed either as a percentage or a value in Data Points Per Second (DPPS).
If a metric, single service, pod, or environment begins to emit a high volume of data that pushes the system over its persisted writes limit, a penalty applies to the pool containing the emitted metric. Pools that haven't exceeded their quota aren't penalized.
Metrics within a pool are guaranteed at least the defined percentage of system writes at all times. Individual pool quotas must sum to less than or equal to the capacity limit. If your entire Chronosphere tenant is under the capacity limit, an individual pool can exceed its defined quota without incurring a penalty, and Chronosphere Observability Platform allocates the remaining capacity to the Default Pool.
Chronosphere recommends using the fewest number of pools possible for administrative ease. Ten or fewer pools is adequate for most use cases.
View quotas and pools
Find metric pools defined in your instance on the:
If you haven't configured any metric pools, Observability Platform shows a single Default Pool.