opentelemetry-operator
opentelemetry-operator copied to clipboard
Kubernetes Operator for OpenTelemetry Collector
### Component(s) target allocator ### What happened? Title: Bug in Apply Method: Modified lset Not Assigned Back to tItem.Labels Description: There is a bug in the Apply method of relabelConfigTargetFilter...
### Component(s) TargetAllocator ### What happened? ## Description When the service/pod monitors use basic auth and read the keys from secrets, it is able to get them using the new...
### Component(s) target allocator ### What happened? ## Description I wanted to test whether metrics are preserved during TargetAllocator rebalancing, so I scaled the number of OpenTelemetryCollector replicas from 2...
### Component(s) auto-instrumentation ### Is your feature request related to a problem? Please describe. As a user of OpenTelemetry on K8s, I likely have a mixture of applications which have...
### Component(s) _No response_ ### Describe the issue you're reporting This instruction removes the path of the source file outside the repository.
Fixes #3583
This feature gate controls whether the OpenTelemetryCollector CR with an emebedded target allocator configuration internally creates a TargetAllocator CR resource instead of managing the manifests directly. - [x] Promoted to...
### Component(s) auto-instrumentation ### What happened? ## Description When deploying the instrumentation CR with values under spec.env, the values do not seem to propagate down/overwrite default configuration ## Steps to...
We currently take target labels unmodified from both service discovery and config. Prometheus actually does some post-processing of target labels, which normally wouldn't be an issue for target allocator, as...
### Component(s) collector ### What happened? ## Description The service for monitoring used to be created with a port number defined in `.spec.config.service.telemetry.metrics.address`. ```bash > kubectl get opentelemetrycollectors.opentelemetry.io logs -o...