search

openzipkin / zipkin-dependencies

Spark job that aggregates zipkin spans for use in the UI
Apache License 2.0
176 stars 81 forks source link

Wrong connection on dependency page #159

Closed Igor-lkm closed 4 years ago

Igor-lkm commented 4 years ago

Problem: Wrong connection on dependency page.

Spans first to last of a trace:

id parentId kind name ocalEndpoint.serviceName
a5de7eaf3ba9da13 - SERVER kong.request kong-gateway
c76dd63b23b36e85 a5de7eaf3ba9da13 CLIENT kong.proxy Service-A-Gateway
c76dd63b23b36e85 a5de7eaf3ba9da13 SERVER post Service-A
6788097f19803f4d c76dd63b23b36e85 CLIENT post Service-A
6788097f19803f4d c76dd63b23b36e85 SERVER post Service-B
c5d172ee032a4231 6788097f19803f4d CLIENT get Service-B
c5d172ee032a4231 6788097f19803f4d SERVER get Service-C

How should it be:

Service-A-Gateway - Service-A - Service-B - Service-C

what i get:

Service-A-Gateway - Service-A - Service-B
                       |
                    Service-C

Somehow we have dependency between A and C.

Discovery page looks fine:

Screenshot 2019-12-16 at 11 30 40

My setup:

1) zipkin:2.19.1 2) openzipkin/zipkin-dependencies:2.4.1 3) zipkin-instrumentation-koa@^0.19.1 4) zipkin-instrumentation-request-promise@^0.19.1 5) Kong@1.3

Thank you!

Igor-lkm commented 4 years ago

sorry, messed up contexts...