The C++ Jaeger client always populates the "ip" tag with 127.0.0.1

[jaegertracing]

The C++ Jaeger client always populates the "ip" tag with 127.0.0.1

[isaachier]

Yes I agree that implementing environment variable overrides is necessary for this case and others. Maybe we can expand this issue to cover all of the environment variable overrides listed here: https://www.jaegertracing.io/docs/1.6/client-features.

[tudor]

Yes, I'm a bit miffed that I have to set both environment variables (for the Java servers) and generate a YAML config (for the C++ servers).

[tudor]

@isaachier: This also has the side effect of disabling clock skew adjustment in the collector, as the clock skew adjustment algorithm assumes that spans with the same value for the "ip" tag come from the same host, and thus do not need adjustment. https://github.com/jaegertracing/jaeger/blob/50429cb55aee9280e39621a0b5aae3c2afe5d190/model/adjuster/clockskew.go#L77

[tudor]

The Java client resolves the local hostname (as would be returned by gethostname()) instead of using the first AF_INET interface: https://github.com/jaegertracing/jaeger-client-java/blob/41a9d104a83bfcf7ed388daf4724dcd7f68237ff/jaeger-core/src/main/java/io/jaegertracing/internal/JaegerTracer.java#L107

[yzpangu]

The latest version doesn't solve this problem. How did you solve it？
Trying to build master branch code won't do either