by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:48
    slikk66 closed #176
  • 18:48
    slikk66 commented #176
  • 16:54
    slikk66 commented #176
  • 16:52
    slikk66 opened #176
  • 15:50
    Ghost---Shadow commented #201
  • 15:49
    Ghost---Shadow commented #201
  • 15:36
    jcchavezs commented #201
  • 15:33
    poorejc commented #441
  • 15:23
    Ghost---Shadow commented #201
  • 14:31
    jcchavezs closed #175
  • 14:31
    jcchavezs commented #175
  • 14:30
    jcchavezs commented #183
  • 14:00
    Travis openzipkin/zipkin-go (master) broken (754)
  • 13:43
    jcchavezs commented #205
  • 13:43
    jcchavezs closed #205
  • 13:42
    jcchavezs closed #238
  • 13:42
    jcchavezs reopened #274
  • 13:42
    jcchavezs closed #270
  • 13:42
    jcchavezs closed #274
  • 13:42
    jcchavezs closed #289
Yehuda Makarov
@yehudamakarov
i'll upload more precise snippets. unless you're ok with a diagram
Adrian Cole
@adriancole
I think it is best to validate that this is a relevant support channel for you
I've so far not seen anything related to the code we maintain in your description, except for the word zipkin
this channel is volunteer run, so it is best to get you where you need to go. understand troubleshooting things can be frustrating, but not sure how much we can help on something we have no responsbility over either
so first what is "Zipkin tracer that sends to Stackdriver" this will start the triage
many things call themselves zipkin, and when you said that option seems like it isn't likely something we wrote
Yehuda Makarov
@yehudamakarov
that's what i'm trying to do.
https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#enable-opentracing
That shows how ingress-nginx can send to a zipkin host.
I have a docker.io/openzipkin/zipkin-gcp container in my cluster.
From this, being that it is sending the logs to stackdriver, I can see a trace from ingress-nginx. that request went to my c# api.
you've helped me with this container in the past... either way, for now, I'm just trying to understand if usually people connect all the spans under one trace, or not necessarily
because any tracing library i try to use in code, doesn't pick up the trace that already started in the ingress and simply add to it with spans. It starts a new trace
Adrian Cole
@adriancole
in general it sounds like you have a propagation problem
so either the ingress-nginx isn't sending b3 headers, or whatever your c# api is isn't reading them
based on your description of the problem anyway (start a new trace problem)
so it is important to know what c# thing you are using, which headers nginx are sending and if that thing supports reading those or not
ex there are two forms of B3 headers (multi and single header) https://github.com/openzipkin/b3-propagation
to triage you can start with this.. if the zipkin-gcp thing is receiving spans, that's good. it cannot affect propagation though
that will be the seam between your apps in this case nginx and the next thing
@nicmunroe has a nice piece on the general art of troubleshooting which applies regardless of library type https://medium.com/nikeengineering/hit-the-ground-running-with-distributed-tracing-core-concepts-ff5ad47c7058
and to answer directly, yes it is the intent to connect all spans in one http request together with the same trace ID
this is universally the case with http microservices
Adrian Cole
@adriancole
for our projects we usually use known working examples.. library choice matters a lot, and without knowing the library we don't know if it works.
adriancole @adriancole has to go for a bit
Yehuda Makarov
@yehudamakarov
thank you for all the info. I have the answers i need. the request after it goes through the nginx ingress has b-3 headers. Maybe i will trouble shoot more within the zipkin library in c#. (which is https://github.com/openzipkin/zipkin4net)
Adrian Cole
@adriancole
yeah that would be odd indeed if the latter didn't work with b3 propagation. you can have a look at the examples directory there.. the project is lightly maintained, but it is used (notably by MdSol)
Adrian Cole
@adriancole
@yehudamakarov unsolicited 2p is to run the examples behind your nginx then compare (assuming they continue the trace)
Yehuda Makarov
@yehudamakarov
@adriancole i will let you know how this goes. thanks for all the advice
Adrian Cole
@adriancole
:thumbsup:
Josh Young
@mandragorn

continuing the docker/zipkin/eureka saga I switched to the other Dockerfile strategy:

# We copy files from the context into a scratch container first to avoid a problem where docker and
# docker-compose don't share layer hashes https://github.com/docker/compose/issues/883 normally.
# COPY --from= works around the issue.
FROM scratch as scratch

COPY . /code/

FROM openzipkin/zipkin-builder as built

COPY --from=scratch /code /code

WORKDIR /code

RUN mvn -B --no-transfer-progress package -DskipTests=true

WORKDIR /zipkin-eureka

RUN cp /code/target/eureka-zipkin-client-*-module.jar eureka-zipkin-client-module.jar && \
  (mkdir eureka-zipkin-client-module && cd eureka-zipkin-client-module && jar -xf ../eureka-zipkin-client-module.jar) && \
  rm eureka-zipkin-client-module.jar

RUN cp /code/eureka-client.properties eureka-client.properties

FROM openzipkin/zipkin:master
MAINTAINER Zipkin "https://zipkin.io/"

COPY --from=built /zipkin-eureka/ /zipkin/

ENV MODULE_OPTS="-Dloader.path=eureka-zipkin-client-module -Dlogging.level.*=DEBUG -Dlogging.level.org=DEBUG -Dlogging.level.com=DEBUG -Dlogging.level.io=DEBUG -Dspring.application.name=zipkin"

As was suggested by @adriancole further up in the channel (Thank you!) and with that I upped the logger to DEBUG. That gave this helpful info on what spring was loading:

============================
CONDITIONS EVALUATION REPORT
============================
Positive matches:
-----------------
....
Negative matches:
-----------------
 ...
   EurekaDiscoveryClientConfigServiceBootstrapConfiguration:
      Did not match:
         - @ConditionalOnClass did not find required class 'org.springframework.cloud.config.client.ConfigServicePropertySourceLocator' (OnClassCondition)
...

I tried also adding spring-cloud-starter-config-client, but that gave issues with missing dependencies. Unfortunately I'm new to spring boot (just started playing with all this yesterday) so I'm not sure where to go from here.

Currently I have eureka setup for service discover in spring boot mostly because that was the first tutorial I was looking at... would Consul be easier to setup with the zipkin docker image? Up until this Eureka has been easy to setup for the other services I was working with, but I haven't tried consul.

Adrian Cole
@adriancole
something that doesn't rely on java types to perform service registration and lookup is easier indeed
what you probably have not tuned right is the jar added to the loader path. it likely is missing an inner thing including the cloud-config library
the "module" jar should have packed that up in other words
that all said, yeah anything that doesn't require modifications to binaries is easier
Thierry Peng
@thpeng
Hi. Is there a way to secure the collector endpoint out-of-the-box in zipkin (e.g. basic auth, oauth ..)?
Adrian Cole
@adriancole
@thpeng if you are using kafka, sure it has some natively supported stuff, as does rabbitmq I think. http we didn't choose to bake in something as there are major issues with basic auth, credential rotation etc we didn't want to step into. Instead just use a proxy that has the features you need
you can call it mesh :)
Thierry Peng
@thpeng
@adriancole thanks. We're stuck with the rest endpoint because of private PaaS setup reasons. I thought about moving zipkin behind the spring-cloud-gateway, securing all non-GET endpoints (allowing the usage of the ui freely). As far as I have seen, the zipkin ui does not use other methods (upload excluded). But then we have also to modify the span reporter in sleuth (using a customized rest template).
Adrian Cole
@adriancole
good thing is that the ui and everything it needs is under /zipkin and only GET is needed
the upload is actually in-browser.. doesn't get to the server
so the POST thing is indeed collector-only (also under /api/v2/spans, not /zipkin) and that narrows the thing to pin
Thierry Peng
@thpeng
ok, thanks for the url hint. I will investigate further
Adrian Cole
@adriancole
and also because we chose to not proliferate BASIC, we also chose to leave open how to modify requests vs bake in basic which isn't actually supported on the backend by default
ex some SaaS offerings run zipkin clones and have different auth mecahnisms
good luck!
Jiten Vij
@jitenvij1992
I have configured brave for trace id and span id in spring web-mvc project. It is showing the server call but it is not showing the call which I am making from spring mvc project to spring boot project because of which trace id is different in spring MVC and spring boot. Please advise.
There should be two span for one trace Id.. one will refer to the server call and another to the client call
chris vale
@crispywalrus
If there’s anyone else here using zipkin-finagle I’ve got a PR open #78 to update Scala to 2.13. My maven foo isn’t strong enough to cross build between scala 2.12 and 2.13 so if you know how I’d love to hear about it. Otherwise I suppose I will have to publish both with differing (?) tags.
meustrus
@meustrus
:wave: I'm trying to set up Zipkin and am looking at storage options
which suggests my options are, Elasticsearch, X-Ray, Stackdriver, Logz.io, Scouter APM, Kafka, or Haystack.
But the default storage backend is MySQL, so I feel like I'm missing something. Architecture documentation suggests I should be able to use Cassandra as well: https://zipkin.io/pages/architecture.html#storage
So...is there somewhere I could find all the storage options and how to configure them?