Redaction with `blocked_key_patterns` doesnt work as expected

[vinzee]

Component(s)

processor/redaction

What happened?

Description

I am trying to redact metric attributes in otelcol using the redaction processor. but it did not work as expected.

Steps to Reproduce

# Config 1: multiple explicit regexes
redaction:
  allow_all_keys: true
  blocked_key_patterns:
    - .*password.*
    - .*token.*

# Config 2: single alternation regex
redaction:
  allow_all_keys: true
  blocked_key_patterns:
    - .*(password|token).*

Ingested metrics with attributes:

host: my_host
my_password: exposed
token: abc

Expected Result

host: my_host
my_password: ****
token: ****

Actual Result

host: my_host
my_password: exposed
token: abc

Collector version

0.135.0

Environment information

Environment

OS: 20.04.1-Ubuntu

OpenTelemetry Collector configuration

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  redaction:
    blocked_key_patterns:
      - .*(password|token).*

exporters:
  debug:
    verbosity: detailed

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [redaction]
      exporters: [debug]

Log output

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• processor/redaction: @dmitryax @mx-psi @TylerHelmuth

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[odubajDT]

Hello, thanks for reporting this issue. Do I understand correctly that the config 1 -> multiple explicit regexes works as expected, but the issue is present on config 2 -> single alternation regex ?

Are the metric attributes present on resource level, metric level or scope level?

I can potentially see a problem with masking of scope level attributes, but not on metric and resource levels. Can you please confirm this?

Thank you!

[odubajDT]

Opened a PR to fix an issue about missing redaction of scope level attributes. @vinzee can you please confirm this is the problem you are experiencing, or it's a different one?

Thank you!