You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grafana/agent imports OpenTelemetry Collector as a library, where it's possible to spawn many OpenTelemetry Collectors in-memory from the same process.
Previously, this was done through a fork of OpenTelemetry Collector which exported all internal packages. As of v0.67.0, the internal APIs we were previously using were made completely internal (e.g., no longer exposed even at the package level), so we have to migrate to using the public APIs.
As far as I can tell, the only thing we're missing is the ability to pass a custom MeterProvider and TraceProvider to the otelcol package (which would eventually get propagated to service.Service). We need to pass custom MeterProviders and TraceProviders to be able to distinguish which in-memory OpenTelemetry Collector component metrics are coming from.
Would adding this capability be accepted so we can upgrade to the latest release?
grafana/agent imports OpenTelemetry Collector as a library, where it's possible to spawn many OpenTelemetry Collectors in-memory from the same process.
Previously, this was done through a fork of OpenTelemetry Collector which exported all internal packages. As of v0.67.0, the internal APIs we were previously using were made completely internal (e.g., no longer exposed even at the package level), so we have to migrate to using the public APIs.
As far as I can tell, the only thing we're missing is the ability to pass a custom MeterProvider and TraceProvider to the otelcol package (which would eventually get propagated to
service.Service
). We need to pass custom MeterProviders and TraceProviders to be able to distinguish which in-memory OpenTelemetry Collector component metrics are coming from.Would adding this capability be accepted so we can upgrade to the latest release?
opentelemetry-collector/otelcol/collector.go
Lines 64 to 87 in 2fc6b0e
The text was updated successfully, but these errors were encountered: