Consumption tracking
The Consumption tab captures the current consumption rates across all license dimensions, compared to your license limits. These statistics display across two selectable tabs for Snapshot and overall Trends:- Snapshot is an overview of your current license usage. When selected, this page displays each licensing statistic as a percentage of your contract limit, along with a graph for that statistic over a pre-selected time period.
- Trends explains how your license usage has changed over the selected time period, grouped and graphed by telemetry type.
Metrics consumption
Use the License Overview to track trace consumption against your metrics license dimensions:-
On the Snapshot page, the Metrics consumption section displays aspects of
processed, persisted, and matched metrics data, measured in bytes. Panels also
display this information for histogram data. These panels include:
- Current percentage gauges for persisted writes, matched writes, and persisted cardinality that display consumption versus capacity.
- Seven-day trend lines that plot consumption against capacity so you can spot trends from week to week.
- On the Trends page, you can view metrics consumption trends in higher resolution. If your organization uses consumption-based pricing, click the link to view consumption trends in the Consumption page.
Tracing consumption
Use the License Overview to track trace consumption against your tracing license dimensions:-
On the Snapshot page, the Traces consumption section displays aspects of
processed and persisted tracing data, measured in bytes. These include:
- Daily average rates per second
- Month-to-date cumulative trends
- On the Trends page, you can view trace consumption trends in higher resolution. If your organization uses consumption-based pricing, click the link to view consumption trends in the Consumption page.
Logs consumption
Use the License Overview page to track log consumption against your logs license dimensions:-
On the Snapshot page, the Logging consumption section displays the
following panels and graphs:
- Percentage of persisted writes and processed writes consumed against your full licensing contract.
- Elapsed time against your full contract. Compare the percentage of persisted writes and processed writes consumption against the time elapsed to understand your true consumption rate.
- Daily persisted and processed log data over the past 30 days.
- Cumulative trend of persisted data and processed data against the license limit, over the life of your licensing contract.
- On the Trends page, you can view log consumption trends in higher resolution. Trends display for the last seven days by default. The Persisted limit displays the number of logs that can persist per minute in your tenant. If your organization uses consumption-based pricing, click the link to view consumption trends in the Consumption page.
Events consumption
Use the License Overview to track events consumption against your change events license dimensions:- On the Snapshot page, the Events consumption graph for Persisted Capacity displays the percentage of events consumed against your events license capacity. To filter change events by different attributes, click Go to Changes Explorer to open the Changes Explorer page.
- On the Trends page, you can view event consumption trends in higher resolution. The Persisted capacity limit displays the number of events that can persist per minute in your tenant. This limit is enforced and can incur penalties if exceeded. In certain circumstances, this limit can exceed the license limit temporarily. The Capacity limit displays the number of events that can persist per minute, as defined by your the license in your contract with Chronosphere. The current consumption percentage displays a decimal ratio of persisted data against your per-minute license limit for the selected time period. This value is calculated by dividing the persisted events per minute by the number of events that can persist per minute, defined by the license limit. Use this information to understand the relationship between your persisted data consumption and the defined license limit.
Credits consumption
This feature isn’t available to all Chronosphere Observability Platform users and
might not be visible in your app. For information about enabling this feature in your
environment, contact Chronosphere Support.
- Credit consumption (full contract): The percentage of total contracted credits consumed to date.
- Elapsed time in contract: The percentage of the contract period that has elapsed. Compare this against credit consumption to gauge spend rate.
- Credits cumulative trend: A stacked line chart of cumulative credit usage over the life of the contract.
- Credit monthly consumption: A bar chart of credits consumed per month.
The Credit consumption section displays for any of your telemetry types that use
consumption pricing and credits. For any telemetry data that uses capacity pricing,
or consumption pricing without credits where you purchase bytes, this section doesn’t
display. If a credit contract has expired or is no longer active, a message directs
you to the Consumption page instead.
Metrics
| Resource | Unit | Description |
|---|---|---|
| Persisted series | Million time series | A time series, defined as a combination of metric name and labels, that is persisted to storage. One persisted series is incurred for a time series if no identical time series have been persisted in the last 48 hours. Pricing varies by storage retention. |
| Persisted datapoints | Billion datapoints | An individual, timestamped datapoint that is persisted to storage. Pricing varies by effective datapoint resolution, which is the average time between consecutive persisted datapoints of a time series. |
| Matched datapoints | Billion datapoints | A datapoint matched for aggregation. One matched datapoint is incurred for each aggregation rule matched for each datapoint. |
| Persisted histogram datapoint buckets | Billion buckets | A bucket within a histogram datapoint that is persisted to storage. One persisted histogram datapoint bucket is incurred for each non-zero bucket within a persisted histogram datapoint. |
| Matched histogram datapoint buckets | Billion buckets | A bucket within a histogram datapoint matched for aggregation. One matched histogram datapoint bucket is incurred for each non-zero bucket within a matched histogram datapoint. |
Logs
| Resource | Unit | Description |
|---|---|---|
| Persisted bytes | Gigabyte | Log bytes stored in the database. |
| Processed bytes | Gigabyte | Log bytes matched for transformation and reshaping. |
Traces
| Resource | Unit | Description |
|---|---|---|
| Persisted bytes | Gigabyte | Trace bytes stored in the database. |
| Processed bytes | Gigabyte | Trace bytes matched for transformation and reshaping. |