Hi. I’ve been working on an open source project called Kronicle that includes an integration with Zipkin. Here’s some info in case any is interested.
It combines dependency data from Zipkin with dependencies defined in YAML to render an interactive architecture diagram with filters: https://demo.kronicle.tech/all-components/dependencies
It uses Zipkin traces to render “call graphs”: https://demo.kronicle.tech/components/kronicle-service/call-graphs
It uses Zipkin traces to calculate response times: https://demo.kronicle.tech/components/kronicle-service/response-times
Kronicle uses Zipkin’s Get Traces API endpoint rather than Zipkin’s Get Dependencies API endpoint, as the data from the Get Traces endpoint is much richer.
There’s more info available on https://kronicle.tech
Context is single developer local desktop using containers. Right now we have OpenTelemetry data streaming to zipkin. Following the Zipkin quickstart we are here:
:: version 2.23.4 :: commit 3827477 ::2021-10-20 21:07:13.735 INFO [/] 1 --- [oss-http-*:9411] c.l.a.s.Server : Serving HTTP at /[0:0:0:0:0:0:0:0%0]:9411 - http://127.0.0.1:9411/
Terminating due to java.lang.OutOfMemoryError: Java heap spaceAs best we can tell this might be (but we really aren't sure):
openzipkin/zipkin-dependencies#143
We appreciate any hints or tips.
1 reply
Hello, again. I got the following errors when I tried to build a local docker image (on an amd64 machine):
$ git clone https://github.com/openzipkin/zipkin.git
$ cd zipkin
$ ./build-bin/docker/docker_build openzipkin/zipkin:test
> [install 5/5] RUN /code/build-bin/maven/maven_build_or_unjar io.zipkin zipkin-server master exec && mv zipkin-server zipkin && /code/build-bin/maven/maven_build_or_unjar io.zipkin zipkin-server master slim && mv zipkin-server zipkin-slim:
#17 0.412 *** Building snapshot from source...
#17 43.30 [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.11.0:npm (npm lint) on project zipkin-lens: Failed to run task: 'npm run lint' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 254 (Exit value: 254) -> [Help 1]Any ideas to solve this? There should be some prerequisites before running the command?
operable program or batch file.
6.14.15
1 reply
If you want to send data to ZIpkin you need to add
spring-cloud-sleuth-zipkin, check the docs for a full example: https://docs.spring.io/spring-cloud-sleuth/docs/current/reference/htmlsingle/#how-to-set-up-sleuth-with-brave-zipkin-http
jaeger-collector_1 | {"level":"debug","ts":1636027002.7439644,"caller":"handler/thrift_span_handler.go:130","msg":"Zipkin span batch processed by the collector.","span-count":1}
jaeger-collector_1 | {"level":"debug","ts":1636027002.7450535,"caller":"app/span_processor.go:152","msg":"Span written to the storage by the collector","trace-id":"0000000000000005af7183fb1d4cf5f2","span-id":"352bff9a74ca9ad2"}
- kind: Deployment
apiVersion: apps/v1
metadata:
name: zipkin
namespace: zipkin
labels:
app: zipkin
spec:
replicas: 1
selector:
matchLabels:
app: zipkin
template:
metadata:
labels:
app: zipkin
spec:
containers:
- name: zipkin
image: 'openzipkin/zipkin:latest'
ports:
- hostPort: 9411
containerPort: 9411
protocol: TCP
env:
- name: ES_HOSTS
valueFrom:
configMapKeyRef:
name: zipkin-config
key: es_hosts
- name: STORAGE_TYPE
valueFrom:
configMapKeyRef:
name: zipkin-config
key: storage_type - kind: Service
apiVersion: v1
metadata:
name: zipkin-service
namespace: zipkin
spec:
ports:
- protocol: TCP
port: 80
targetPort: 9411
nodePort: 32733
selector:
app: zipkin
type: NodePort - kind: Ingress
apiVersion: extensions/v1beta1
metadata:
name: zipkin-ingress-config
namespace: zipkin
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
rules:
- host: examplehostname
http:
paths:
- path: /zipkin(/|$)(.*)
pathType: ImplementationSpecific
backend:
serviceName: zipkin-service
servicePort: 80
1 reply
{
"status" : "DOWN",
"zipkin" : {
"status" : "DOWN",
"details" : {
"ElasticsearchStorage{initialEndpoints=https://xyz.es.amazonaws.com, index=zipkin}" : {
"status" : "DOWN",
"details" : {
"error" : "java.lang.IllegalArgumentException: Elasticsearch versions 5-7.x are supported, was: 1.0"
}
}
}
}
}
1 reply
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292) ~[?:1.8.0_242]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308) ~[?:1.8.0_242]
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:607) ~[?:1.8.0_242]
at java.util.concurrent.CompletableFuture.uniApplyStage(CompletableFuture.java:628) ~[?:1.8.0_242]
at java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:1996) ~[?:1.8.0_242]
at java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:110) ~[?:1.8.0_242]
at zipkin2.storage.cassandra.internal.call.ResultSetFutureCall.doEnqueue(ResultSetFutureCall.java:91) ~[zipkin-storage-cassandra-2.23.3-8.jar!/:2.23.3-8]
1 reply
Hello people !
We're going to use zipkin, and we're wondering which backend to choose between cassandra and elasticsearch. I couldn't find much information detailed for zipkin's usage, are there some guidelines somewhere to help us with this choice ? pros and cons, performances or whatever
cheers !
5 replies
9 replies
Hello, apologies if it's a stupid question, but we've instrumented a chain of services such as A -> POST -> B -> POST -> C. My tracing json contains details for this chained call, but on the Zipking UI I can only see the calls from A -> B.
Would be correct to expect that call B -> C should be shown on the same zipkin screen, as a child node of service A?
5 replies
/zipkin/traces/{traceId}