You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@rlanore the filterprocessor already handles metric names with colons as it is doing a string lookup. Make sure the metrics you want to keep have the extact name namespace_cpu:kube_pod_container_resource_limits:sum. You can use a debugexporter with verbosity: detailed to view the data as the filterprocessor will see it.
hummm ok I did not understood use of colon into promql. It's not the name of metrics but a recording rule computed at prometheus level. So with only 'kube_pod_container_resource_limits' in the include statement and the recording rule this works.
Sorry
Component(s)
processor/filter
What happened?
Description
Opentelemetry drop my metric if it contain colon in it's name when use processors/filter include feature
Steps to Reproduce
Deploy last opentelemetry k8s operator and add opentelemetry colector manifest
Expected Result
I must see all metric on sdout
Actual Result
I see only 'up' metric
Collector version
0.96.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: