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

Otel Collector does not support metric receiver although docs advertise that it does. #1425

Open
bhaskarbanerjee opened this issue Jul 12, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@bhaskarbanerjee
Copy link

Describe the bug
OTel Lambda Collector docs say that the collector extension allows lambdas to use the OpenTelemetry Collector Exporter to send traces and metrics to any configured backend while Telemetry API Receiver document says.

The receiver is configured only for traces as seen here

Is this a miss or intentional? And why is it advertised like it is, if this is intentional.

I do see a PR in progress to add support for Logs

Steps to reproduce
Added python proto layer. Added otel collector layer. There is manual instrumentation of custom metrics from the lambda code.
config.yaml looks like:

receivers:
  otlp:
    protocols:
      http:
 
exporters:
  logging:
    loglevel: debug
  otlp:
    endpoint: enterprise.otelcollector.gateway.com
 
service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [logging, otlp]
    metrics:
      receivers: [otlp]
      exporters: [logging, otlp]

processors:
  batch:
    send_batch_max_size: 100
    send_batch_size: 10
    timeout: 2s

What did you expect to see?
Per the documentation, we expected it to work for both traces and metrics (custom metrics)

What did you see instead?
Only traces were exported and collector threw clear error on endpoint /v1/metrics saying it has reached max number of retries.

What version of collector SDK version did you use?
Version

What language layer did you use?
Python

Additional context
No

@bhaskarbanerjee bhaskarbanerjee added the bug Something isn't working label Jul 12, 2024
@bhaskarbanerjee
Copy link
Author

@tylerbenson @nslaughter can you please help on my above query?

@rapphil
Copy link
Contributor

rapphil commented Jul 22, 2024

I'm a bit confused,

threw clear error on endpoint /v1/metrics saying it has reached max number of retries.

This indicates that enterprise.otelcollector.gateway.com does not have an metrics pipeline with an OTLP receiver and that the lambda layer is trying to export the metrics.

One simple way to verify this is the case is to only have the logging exporter in the collector lambda configuration metrics pipeline and then verify in the logs that the metrics are being generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants