Selectively blocking metrics originating from the Wavefront operator with Wavefront Proxy preprocessor rules
Article ID: 390480
Updated On:
Products
Issue/Introduction
This article demonstrates how to setup preprocessor rules with the Wavefront Proxy to selectively block metrics being generated from the Wavefront Operator itself.
Environment
Wavefront Operator
Resolution
To achieve your goal of disabling selected metrics from the Wavefront Operator, for example, certain control plane metrics, you need to add a custom resource file with preprocessor rules so that the proxy knows which metrics to reject/block.
Please refer to the following link for an example of preprocessor rules: Wavefront Proxy Preprocessor Rules YAML
Here’s an example of what two blocking rules could look like:
rules.yaml: |
'2878':
- rule : block-controlplane-histogram
action : block
scope : metricName
match : "kubernetes.controlplane.workqueue.*"
- rule : block-controlplane-histogram1
action : block
scope : metricName
match : "kubernetes.controlplane.apiserver.*"
- kubernetes.controlplane.apiserver.request.duration.seconds.m
- kubernetes.controlplane.workqueue.queue.duration.seconds.m
Additional Information
You just need to add the metric names you want to block to the match sections in the rules. Once configured, you can check the logs to see histograms are being blocked by running the following command:
The logs should show entries like:
Feedback
