Skip to content

Conversation

pavolloffay
Copy link
Member

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 99.953% when pulling 6cb8a44 on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c21fe7d on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

@pavolloffay pavolloffay closed this Sep 4, 2017
@pavolloffay pavolloffay reopened this Sep 4, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c21fe7d on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

if a.Host != nil && a.Host.ServiceName != "" {
return a.Host.ServiceName, a.Host.Ipv4, nil
}
}
Copy link
Member

@yurishkuro yurishkuro Sep 5, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you're adding this you obviously ran into an issue, but I am curious that kind of binary annotation (aside from LOCAL_COMPONENT already checked for above) could be considered a reliable source of service name/ip?

NB a comment above this loop would be good explaining.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added a comment, basically tracer can send a span with just one binary annotation, see also liked issue it happened with correct OT instrumentation and brave-opentracing.

@yurishkuro
Copy link
Member

test seems to fail with dial tcp: lookup zipkin-brave-json on 127.0.0.11:53: no such host - why such a strange port number, 53?

@yurishkuro
Copy link
Member

looks great if we can get it to work!

@pavolloffay
Copy link
Member Author

test seems to fail with dial tcp: lookup zipkin-brave-json on 127.0.0.11:53: no such host - why such a strange port number, 53?

It was late I forgot to push the latest image. Now it should work.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling de8b785 on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

Copy link
Contributor

@black-adder black-adder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome

@@ -9,6 +9,8 @@ services:
- node
- java
- python
- zipkin-brave-json
- zipkin-brave-thrift

environment:
- WAIT_FOR=test_driver,go,node,java,python
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should wait for zipkin-brave-json/zipkin just in case (assuming they have a health check endpoint)

@@ -178,6 +178,12 @@ func (td toDomain) findServiceNameAndIP(zSpan *zipkincore.Span) (string, int32,
return a.Host.ServiceName, a.Host.Ipv4, nil
}
}
// Tracer can also report a span witch just binary annotation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/witch/with

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d5a5f9d on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

@pavolloffay pavolloffay closed this Sep 5, 2017
@pavolloffay pavolloffay reopened this Sep 5, 2017
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d5a5f9d on pavolloffay:zipkin-integration-tests into 413942a on uber:master.

@pavolloffay pavolloffay force-pushed the zipkin-integration-tests branch from d5a5f9d to f285fd1 Compare September 6, 2017 10:35
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f285fd1 on pavolloffay:zipkin-integration-tests into d94ab57 on uber:master.

@pavolloffay
Copy link
Member Author

The repo has been moved to https://github.com/jaegertracing/xdock-zipkin-brave

@pavolloffay
Copy link
Member Author

this should be ready for re-review/merge.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 99.953% when pulling 033c1b8 on pavolloffay:zipkin-integration-tests into d94ab57 on uber:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c393ce7 on pavolloffay:zipkin-integration-tests into 5d5a16b on uber:master.

@yurishkuro yurishkuro merged commit d60f25c into jaegertracing:master Sep 7, 2017
ideepika pushed a commit to ideepika/jaeger that referenced this pull request Oct 22, 2017
isaachier pushed a commit to isaachier/jaeger that referenced this pull request Nov 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants