-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling WAL is not exporting metrics to Mimir backend using Prometheus remote write exporter #33238
Comments
Pinging code owners:
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 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
otel-collector-cr.txt
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
The text was updated successfully, but these errors were encountered: