opentelemetry-collector
opentelemetry-collector copied to clipboard
open-telemetry
OpenTelemetry Collector
Resolves [(contrib)#9963](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/9963). Possibly these should be defined in contrib or in a separate file. I'd appreciate feedback on the guidelines themselves as well as appropriate placement in the documentation.
**Description:** This is a proof of concept in support of #4970. A `TelemetryProvider` is defined to support overriding the telemetry on the Collector. A default implementation is provided, but alternatives...
Right now, we do have a "GetID/SetID" on the configuration interface for all our components, this causes the interface to have "mutable" funcs. It would be cleaner from a design...
We have requirement to deploy the otel collector as a service in PCF( pivotal cloud foundry ) to collect telemetry of microservices/applications, like how we deploy in Kubernetes as a...
**Is your feature request related to a problem? Please describe.** If you want to deploy the OpenTelemetry Collector in gateway-mode behind an AWS Application Load Balancer (ALB) to support gRPC...
**Describe the bug** I am doing a basic set up of open telemetry collector and agent. I am using a AWS Network loadbalancer endpoint for the otlp exporter. I was...
Right now batching capability is offered as a processor, and this is extremely generic in our current pipeline model, which is a great thing, but also comes with limitations: 1....
There is a [SetMemoryLimit](https://pkg.go.dev/runtime/debug@master#SetMemoryLimit) in Go runtime since 1.19. It is worth checking if using this is better than the manual limit that we do in the memorylimitprocessor currently. Also...
Per open-telemetry/opentelemetry-collector-releases/pull/164, we want to promote usage of the OpenTelemetry Collector Builder so that people build their own distribution with only the components they use. The only documentation we have...