Replies: 3 comments
-
I face the same problem with the following config, the metrics with processors:
filter:
error_mode: ignore
metrics:
exclude:
match_type: expr
expressions:
- MetricName == "calls" && Label("span_kind") == "SPAN_KIND_CLIENT"
connectors:
spanmetrics:
service:
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [otlp, spanmetrics]
metrics/spanmetrics:
receivers: [spanmetrics]
processors: [filter]
exporters: [prometheus]
|
Beta Was this translation helpful? Give feedback.
0 replies
-
A bug has already been filed for this: |
Beta Was this translation helpful? Give feedback.
0 replies
-
any updates here? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a use case, where I wanted to exclude (filter) metric with particular label combination, I am using otel-collector for collection, processing and exporting metrics
however when I try to write a config, it remove that metric completely with other label combination set as well.
.i.e.
so according to otel Config the receivers is configured as
which gets metric in question as
Now my intention is to remove
node_supervisord_up{group="ServiceD",name="serviceD"} 0
before sending to central Metric aggregator
so I tried, below config of otel-collector processor
Refered from here https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/filterprocessor/README.md
however this results in complete removal of metric name
node_supervisord_up
for other set of services label combination.what configuration could help here to just exculde node_supervisord_up{group="ServiceD",name="serviceD"} 0 before sending to central aggregator from the client.
Beta Was this translation helpful? Give feedback.
All reactions