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
Right now, if you start jaeger v2, it listens for OTLP on localhost. This means docker hostnames don't connect. I would like an option to use an ENV value or CLI arg to listen on all interfaces.
Problem
Without this, I need to write a config file for something easy to do in other go daemons like otel-tui or ollama. I would like a simpler experience, and most importantly one that doesn't risk making other config errors.
Proposal
any env or CLI arg would be great
Open questions
No response
The text was updated successfully, but these errors were encountered:
Requirement
Right now, if you start jaeger v2, it listens for OTLP on localhost. This means docker hostnames don't connect. I would like an option to use an ENV value or CLI arg to listen on all interfaces.
Problem
Without this, I need to write a config file for something easy to do in other go daemons like otel-tui or ollama. I would like a simpler experience, and most importantly one that doesn't risk making other config errors.
Proposal
any env or CLI arg would be great
Open questions
No response
The text was updated successfully, but these errors were encountered: