Skip to main content
After creating shaping rules, you want to understand their impact to ensure they have the intended outcome. Chronosphere Observability Platform provides several tools to understand the impact of the shaping rules you create.

​
Review metric shaping rules

Use the Aggregation Rules UI to understand your existing metric shaping rules and how they affect your environment. Use the shaping impact preview to preview the impact of a rule on your overall system, which helps prevent breaking changes and ensure the rules you create operate as expected. You can then use the Live Telemetry Analyzer to review metrics with a Data phase filter that shows what data was dropped, matched, or rejected by specific rule types. Periodically review the Recommendations page to help identify metrics and labels with no usage or utility over the past 30 days. You can then create drop rules and rollup rules based on the recommendations.
If your organization uses capacity pricing, you can define metrics quotas and pools to assign specific percentages of your total persisted writes limit to pools of metrics.
If you identify data with no business value, apply relabel rules in your collector to adjust which metrics you send from the client side to Observability Platform.

​
Review log control rules

When creating a log shaping rule, enter a filter to display a preview of the log data that the filter matches. This preview lets you confirm that the control rule targets the intended logs before applying the control rule. After creating log shaping rules, use the Logs Usage page to review and understand frequent patterns in your log data. Use this information to identify high-volume, low-utility patterns, and confirm that a pattern’s volume has changed after applying a control rule. You can then create a control rule for a pattern from the Logs Usage page with a defined filter, which ensures you’re matching the correct pattern.

​
Review trace control rules

Use the Trace Control Plane to both create and review the control mechanisms for trace data. After creating datasets, you can view the total processed and persisted bytes for a selected period to understand the data consumption. Before assigning behaviors, run a preview against a specific dataset to understand how it impacts data volume before shaping the data. Select a behavior to view head and tail sampling statistics so you can understand how the behavior affects traces that impact multiple datasets. After creating a trace metric, you can pivot to view similar traces or view similar logs to cross-reference what data the metric is capturing.