Open anushanagireddy0430 opened 2 months ago
Pinging code owners:
exporter/prometheusremotewrite: @Aneurysm9 @rapphil
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Any solution or workaround for persistence would be of help!
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
exporter/prometheusremotewrite
What happened?
To enable persistence we are configuring WAL directory in prometheus remote write exporter. Without WAL able to see metrics being sent to mimir and able to see them in grafana using mimir as datasource. When we enable WAL seeing below error in otel collector pod logs.
Steps to Reproduce
Help me understand in fixing this issue. Also anyway to exec into collector pod to check about persisted data of logs and traces.
Collector version
otel/opentelemetry-collector-contrib:0.95.0
Environment information
Red Hat Enterprise Linux Kubernetes environment
OpenTelemetry Collector configuration
Log output
Additional context
No response