Define a metric pool

• Pool allocations define how much of your total persisted writes license you want allocated to each pool. You can define allocations for each of your licenses individually, or have the same allocations across all pools.
• Pool priorities let you selectively decide which metrics within a given pool to drop first during a penalty scenario. You can set priorities at a global level (for all pools), or individually.
• Pool thresholds are a capability that provide more strict control on persisted cardinality on individual pools. Configure thresholds as a proactive measure to strictly enforce dropping data, even when the overall capacity limit hasn’t been exceeded.
• Match rules are the set of rules that determine which metrics belong to the pool. A metric has to match only one of the rules to belong to the pool. Match rules support glob syntax. See the match_rules defined in the pool thresholds example and the Terraform pool example to understand the rule syntax.

​

License impact

• To understand matched writes quotas and how they applies to individual pools, see the Matched Writes Quotas dashboard.
• To understand persisted cardinality and how it applies to individual pools, see the Persisted Cardinality Quotas dashboard.

​

Pool allocations

Capacity limit - allocations across pools = default pool allocation

• percent_of_license: Specify the percentage of the license to allocate to a pool. This value applies to any license dimensions without fixed_values defined. For example, consider that you allocate 10% of your persisted cardinality license to a pool, and your total persisted cardinality license is 5.0M (million). The allocation for this pool is 5.0M of persisted cardinality (.10*50), so any consumption beyond that value causes metrics to be dropped.
• fixed_values: Specify a fixed value for a license dimension in DPPS. You can set a single fixed value per license dimension. Any fixed_values take precedence over percent_of_license for a given license. If you set any fixed_values, you can specify allocations for both matched writes license and persisted writes. These allocations are available for both standard and histogram metrics. See the CreateResourcePools endpoint for more information.
  The sum of fixed values across all defined pools must be less than or equal to the total allotted capacity, defined by the capacity limit. If your organization exceeds the capacity limit, where the sum of fixed values exceeds total capacity, a penalty is applied to all pools proportional to fixed allocations. A validation in Terraform penalizes any pool that exceeds its allotted quota.In this penalty state, the default pool receives no allocation, and other pools are adjusted down proportionally so that the sum of fixed values is equal to the capacity limit.

​

Configure priority

• High: Metrics dropped last.
• Low: Metrics dropped first.
• Default: Metrics dropped after low priority metrics, but before high priority metrics.

​

Configure global priority

1. On the Metrics Quotas page, click Configure Quotas.
2. Click Edit Global Settings.
3. In the Edit Global Pool Settings dialog, select a label from the Quota Configuration Label dropdown. This label is the label key that defines which keys can be used to create a pool.
4. Select Configure Globally to apply the pool filtering globally, and complete the following fields:
   • Prioritization label: Select a label to change its priority.
   • High priority values: Add a label value, such as production* to ensure metrics with that label value are retained.
   • Low priority values: Add a label value, such as test* to drop metrics of lower importance first.
5. Click Done when finished.
6. Click the Code Config tab.
7. Click Copy to copy the file, or Download to download the file to your computer.
8. Add the definition to a Terraform file, or create a new Terraform file.
9. Run this command to apply the resource:
   Copy

   Ask AI

   terraform apply
   

​

Configure priority per pool

1. On the Metrics Quotas page, click Configure Quotas.
2. Click Edit Global Settings.
3. In the Edit Global Pool Settings dialog, select a label from the Quota Configuration Label dropdown. This label is the label key that defines which keys can be used to create a pool.
4. Select Configure per pool to set priority independently for each pool.
5. Click Done when finished.
6. Edit each pool to set priorities.

​

Pool thresholds

​

All priorities threshold

• The value of this threshold should be greater than or equal to the pool allocation. For example, if the pool allocation is 50%, then the threshold should be 50% or greater. If the threshold value is less than the pool allocation, consider changing the pool allocation instead.
  Setting the threshold to a value that exceeds 100% of the pool allocation can cause multiple pools to exceed their allocation, which can cause your system to hit the cardinality limit and arbitrarily drop data.
• Use a percentage for this value rather than a fixed value in DPPS, especially if you want the threshold value to match the pool allocation. If the threshold is a fixed value, then you must update that value any time the pool allocation or license capacity changes.
• You can set this threshold to a value that exceeds 100% of the pool allocation, which provides a buffer before the threshold limit causes the pool to drop data. This configuration accommodates occasional spikes, or situations when you’re migrating data from one pool to another over a longer period.

​

Low and medium priority thresholds

​

Configure pool thresholds

• If the control team consistently uses approximately 95% of its pool, and you want to prevent an overage from resulting in drops in other pools, set a strict threshold (all_priorities) to 100%.
• If the control team contains data for your most important pool, and you’d rather drop data from all other pools except this one, set strict thresholds for all other pools except the control team pool.
• If the control team often experiments with new series in its development and staging environments, set proactive thresholds to 10% for low priority and 20% for combined low and medium priority data to preserve space for high-priority series.

1. Add the priority_thresholds object to your existing metric pools definition with either Terraform or the CreateResourcePools endpoint.
2. Define the license you want the threshold to operate on. Thresholds support these licenses:
   • PERSISTED_CARDINALITY_STANDARD: Refers to the standard metric license, which measures the current consumption rates across persisted writes, matched writes, and persisted cardinality license dimensions measured against the capacity limit.
   • PERSISTED_CARDINALITY_HISTOGRAM: Refers to the histogram metrics license, which measures the current consumption rate across all histogram metrics license dimensions measured against the capacity limit.
3. Define the thresholds you want to configure, which can be one of the following values:
   • all_priorities: Stop accepting any data (low, medium, and high) at the specified threshold if consumption for the pool exceeds threshold value.
   • default_and_low_priority: Stop accepting low and medium priority data at the specified threshold if low and medium priority data combined exceed threshold value.
   • low_priority: Stop accepting only low priority data at the specified threshold if low priority data exceeds threshold value.
4. Save and apply your metric pools definition.

​

Pool thresholds example

  pool {
    name = "Control Services"
    allocation {
      percent_of_license = 16
      priority_thresholds {
        license = "PERSISTED_CARDINALITY_STANDARD"
        all_priorities {
          percent_of_pool_allocation = 100
        }
        default_and_low_priority {
          percent_of_pool_allocation = 50
        }
        low_priority {
          percent_of_pool_allocation = 25
        }
      }
      priority_thresholds {
        license = "PERSISTED_CARDINALITY_HISTOGRAM"
        all_priorities {
          percent_of_pool_allocation = 100
        }
        low_priority {
          percent_of_pool_allocation = 25
        }
      }
    }
    match_rules = ["service:{${join(",", control_services)}}"]
    priorities {
      high_priority_match_rules = ["cluster:production*"]
      low_priority_match_rules  = ["cluster:test*"]
    }
  }