Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter processor crashes the collector #12206

Closed
corvaglia-alessio opened this issue Jul 9, 2022 · 3 comments
Closed

Filter processor crashes the collector #12206

corvaglia-alessio opened this issue Jul 9, 2022 · 3 comments
Labels
bug Something isn't working priority:p2 Medium processor/filter Filter processor

Comments

@corvaglia-alessio
Copy link

corvaglia-alessio commented Jul 9, 2022

Describe the bug
I'm using the lambda layer for instrumenting a python lambda function. Everything works as expected, even using other processors, but when I enable the filter processor, the collector crashes with the following error:


START RequestId: f565b21c-f901-4bd8-9c1a-4515f65676e9 Version: $LATEST
2022/07/09 09:55:48 [collector] Launching OpenTelemetry Lambda extension, version:  v0.1.0
2022/07/09 09:55:48 Using config file at path /var/task/collector.yaml
2022/07/09 09:55:48 Failed to start the extension: failed to get config: cannot unmarshal the configuration: error reading processors configuration for "filter": 1 error(s) decoding:

* '' has invalid keys: spans
EXTENSION	Name: collector	State: Started	Events: []
END RequestId: f565b21c-f901-4bd8-9c1a-4515f65676e9
REPORT RequestId: f565b21c-f901-4bd8-9c1a-4515f65676e9	Duration: 2415.91 ms	Billed Duration: 2416 ms	Memory Size: 128 MB	Max Memory Used: 32 MB	
RequestId: f565b21c-f901-4bd8-9c1a-4515f65676e9 Error: exit status 1
Extension.Crash

What version did you use?
OpenTelemetry collector v0.54

What config did you use?
The collector config file is the following:

# collector.yaml in the root directory
# Set an environment variable 'OPENTELEMETRY_COLLECTOR_CONFIG_FILE' to
# '/var/task/collector.yaml'

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  filter:
    spans:
      include:
        match_type: strict
        services:
          - my_lambda3
      exclude:
        match_type: strict
        span_names:
          - lambda_function.lambda_handler

exporters:
  logging:
    loglevel: debug
  otlp:
    endpoint: *******
    tls: 
      insecure: true
    headers:
      x-scope-orgid: ******

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [filter]
      exporters: [otlp]

I do not know if it is the right repo to open this issue since it is related both to the filter processor and to the lambda layer.

@corvaglia-alessio corvaglia-alessio added the bug Something isn't working label Jul 9, 2022
@TylerHelmuth
Copy link
Member

pinging @boostchicken @pmm-sumo as code owners

@TylerHelmuth TylerHelmuth added priority:p2 Medium processor/filter Filter processor labels Jul 11, 2022
@boostchicken
Copy link
Member

boostchicken commented Jul 12, 2022

I dont think the spans filter is in 0.54? Only 0.55

Confirmed here in the changelog, please update

https://github.com/open-telemetry/opentelemetry-collector-contrib/releases

@corvaglia-alessio
Copy link
Author

Oh sorry, my mistake! Thanks for the clarification @boostchicken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:p2 Medium processor/filter Filter processor
Projects
None yet
Development

No branches or pull requests

3 participants