opentelemetry-collector
opentelemetry-collector copied to clipboard
open-telemetry
OpenTelemetry Collector
Hi, How I can test below pipeline using some sample payload. Want to test/ensure connector routes the request to corresponding pipeline based on the field 'name'. receivers: webhookevent: endpoint: 0.0.0.0:1111...
#### Description This is the core part of the remote tap concept described here: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34096 This will be used by the new version of the [remotetap extension in contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34872). This...
I’m experiencing intermittent issues with my OpenTelemetry setup, specifically related to exporting metrics to Elasticsearch using the OTLP exporter. The setup involves multiple services that send telemetry data to different...
Hello, Need help with the issue i am facing with below usecase Usecase: Test if we are able to export traces using a local otel collector over ingress to another...
#### Description Add tracing to all the components #### Link to tracking issue Fixes #8804 #### Testing Based on https://github.com/open-telemetry/opentelemetry-collector/pull/8833
#### Description Delete GetExporters on nopHost as it is no longer part of the interface signature. This is a no-op and no change in API exposed directly is present since...
#### Description In #10058 I mentioned: > There is a tangentially related issue with PermanentErrors and the underlying finite state machine that governs transitions between statuses. Currently, a PermanentError is...
I can add a note in the zpages documentation, note that the zpages extension already logs a warning if this happens _Originally posted by @codeboten in https://github.com/open-telemetry/opentelemetry-collector/pull/10892#discussion_r1729446799_
**Describe the bug** Right now, the OTLP HTTP receiver only allows for http2 upgrades if you specify a TLS configuration. This is an issue for environments that terminate TLS before...
Another investigation into https://github.com/open-telemetry/opentelemetry-collector/issues/9429 based on [this strategy](https://github.com/open-telemetry/opentelemetry-collector/pull/10069#issuecomment-2113518403). If we like this approach I can add in the `Must*` functions to enforce pipeline name patterns. It also doesn't really matter...
