Shape your data

When ingesting metrics into Chronosphere, users can experience the challenge of managing the cardinality of persisted data. Metric cardinality is the number of unique time series produced by a combination of metric names and their associated labels. Cardinality is the total number of these combinations. The more combinations there are, the greater a metric's cardinality is, and the more data Chronosphere persists. This can affect your license.

The Chronosphere Control Plane lets you reduce the amount of data retained in your system over time. Downsample to reduce unneeded data, and focus on important metrics.

Manage your data with tools that help you shape that traffic in the following ways:

  • Rules drop data before it reaches Chronosphere, or aggregate and rewrite data into more manageable and usable statistics.
  • Quotas and pools focus usage into selected areas, ensuring retention of critical metrics.

Use the Aggregation rules UI to understand your existing rollup and mapping rules and how they affect your environment.

To better understand what rules are adding or reducing data in your system, use the shaping impact columns in the Aggregation rules UI.

Try changes to the shape of your traffic without risking data increases using shaping impact preview.


The Chronosphere Collector scrapes metrics at specific intervals, based on system configuration. This granularity of metric data can be helpful in diagnostic efforts, but particular issues might not be served by such granularity. If you are able to diagnose production issues using a coarser granularity of metric data, downsampling the data reduces the amount of data persisted to the Chronosphere database.

Downsample data in Chronosphere using these methods:

  • Change the Collector configuration by changing the rate the Collector publishes metrics to the server.
  • Use mapping rules to downsample metrics that aren't aggregated.
  • Use rollup rules to downsample aggregated metrics.