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
@lpetrazickisupgrade I am curious if the issue is with the collector serving the metrics or the prometheus receiver scrapping. Can you reproduce the issue without a prometheus receiver trying to scrape?
@TylerHelmuth Thanks for taking a look! I think the OpenTelemetry Collector process is crashing at startup parsing the config. The pod is in a CrashLoopBackOff. It doesn't get far enough in the startup sequence to respond to network requests. I've included the only log message
Describe the bug
Steps to reproduce
listen tcp: address dead:beef:dead:beef:dead::beef:8888: too many colons in address
What did you expect to see?
Metrics on port 8888
What did you see instead?
What version did you use?
v0.98.0
What config did you use?
Environment
helm.sh/chart: opentelemetry-collector-0.87.2
Image: opentelemetry-collector-contrib:0.98.0
Kubernetes: v1.29.1-eks-b9c9ed7
Additional context
This is a regression. v0.79.0 did not have this issue
The text was updated successfully, but these errors were encountered: