I'm trying to deploy opentelemetry collectors using the opentelemetry operator to scrape Prometheus metrics and send metrics to remote storage using prometheusremotewrite exporter.
It worked when I used the most simple config. Just add scrap jobs to prometheus receiver and use prometheusremotewrite exporter to send metrics.
However, when I tried to set up the otel collector with target allocator, the target allocator didn't generate a proper configmap for collectors.
The configmap generated by the target allocator is called allocator-collector and this configmap only has one key "collector.yaml' with an empty value. Since the configmap is incorrect, the collector pod keeps restarting.
I suppose the target allocator will create a configmap for collectors using OpenTelemetryCollector.spec.config with receivers replaced.
Version ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:v0.66.0
I'm trying to deploy opentelemetry collectors using the opentelemetry operator to scrape Prometheus metrics and send metrics to remote storage using
prometheusremotewrite
exporter.It worked when I used the most simple config. Just add scrap jobs to
prometheus
receiver and useprometheusremotewrite
exporter to send metrics.However, when I tried to set up the otel collector with
target allocator
, thetarget allocator
didn't generate a proper configmap for collectors.The configmap generated by the
target allocator
is calledallocator-collector
and this configmap only has one key "collector.yaml' with an empty value. Since the configmap is incorrect, the collector pod keeps restarting.I suppose the target allocator will create a configmap for collectors using
OpenTelemetryCollector.spec.config
with receivers replaced.Version
ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:v0.66.0
manifest