View allocated pools

The Metrics Quotas page displays existing metrics pools, the persisted writes quota allocated to each pool, and the amount of persisted writes quota consumed by each pool.

Teams can use this information to understand which pools are consuming quota and how much, which pools are at risk of being limited, and how each pool has prioritized its traffic to ensure that only lower priority data drops if the system exceeds its limit while a pool is over its quota.

To review your pools data, in the navigation menu select Managing > Metrics Quotas.

Use the Sort by menu to change the display order. A summary of All Pools always display at the top of the list.

  • Quota consumption: high to low
  • Quota consumption: low to high
  • Name: ascending
  • Name: descending

Use the Search box to find a specific pool.

Select a Time Range to display.

  • Last 7 Days
  • Last 14 Days
  • Last 30 Days

Select a pool name to view data specific to that pool. The Default Pool is the pool containing all otherwise unassigned metrics.

To create and edit quota pools, click Configure Quotas.

Hold the pointer over any sparkline chart to display a dialog with data specific to that day and time. Click the dialog to pin it.

All pools - Persisted writes

When viewing All Pools, you can see system-wide persisted writes quota consumption and the pools consuming the highest percentage of their assigned quotas.

  • Total Limit for persisted writes, in data points per second (DPPS)

  • Average persisted writes in DPPS

  • Current percentage of usage versus your limit

  • A graph of the change over time in the overall consumption of quota, as a percentage of total quota.

  • Overall limit and consumption by pool is a stacked-area sparkline chart of which individual pools are consuming how much quota. Use this to compare pools and better understand which of them are taking the most resources. Hold the pointer over the chart to view the number of data points contributed by each pool at that time.

  • Quota consumption by pool graphs detail the assigned limits and current consumption of that limit for each pool. If one of your pools exceeds its limit, but the overall quota consumption is still 100%, the pool exceeding the limit continues to collect data normally. Hold the pointer over a graph to see incoming data points and the quota limit.

    When the system exceeds the persisted writes limit, Chronosphere enforces the limit by dropping data from pools over their quota.

Select a pool

Click a pool name to view data specific to that pool. The pool's page includes the following details about the pool's quota usage:

  • Services traffic: This graph displays the current percentage of total quota this pool is using, and a graph tracking the usage of the time range.
  • Quota Consumption: Use this graph to track the consumption of quota in DPPS, against the limit.
  • Traffic by service: Use this graph to determine which services configured in this pool generate the most traffic.
  • Traffic Priority: Traffic priority displays in a box chart which shows which priorities have the most traffic, based on priority definitions.

In addition to any named metric pools you define, all instances have a Default pool. You can set the quota for the default pool, but not the name or match criteria. The Default pool matches any metric that isn't matched by another pool. When new metrics which don't match defined pools get assigned to the Default pool.

Quota Configuration Values

This table lists all the label Values matching the pool configuration. and how much DPPS each contributes to the pool quota. In the Default pool, new metrics have the New indicator.