This does not seem to be a Zipkin question, you can ask SLeuth-related questions here: https://gitter.im/spring-cloud/spring-cloud-sleuth
If you want to send data to ZIpkin you need to add
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":"warn","ts":1636027002.7438812,"caller":"handler/thrift_span_handler.go:138","msg":"Warning while converting zipkin to domain span","error":"cannot find service name in Zipkin span [traceID=af7183fb1d4cf5f2, spanID=352bff9a74ca9ad2]"}
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"}
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"}
i have issue zipkin plugin sent span to jaeger collector zipkin 9411/api/v2/spans
Hello community I am having issues accessing the UI for a deployed zipkin on kubernetes through an ingress. For some reason, whenever I try to access the UI (from the path examplehostname/zipkin) I am receiving redirect errors (ERR_TO_MANY_REDIRECTS shown by browser). However, all of the other endpoints appear to be working fine and return the correct information when I curl them (examplehostname/zipkin/info, examplehostname/zipkin/health, etc...) and I have applications which can successfully send tracing data to examplehostname/zipkin/api/v2/spans. The UI is just inaccessible, was wondering if anyone can help?
- 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
Could someone in the community review my PR (https://github.com/openzipkin/zipkin/pull/3384)? I have not received any comments or feedback for the past 15 days since I finalized it.
1 reply
Hey, anybody tried running Zipkin with OpenSearch (AWS' Elasticsearch "fork"). There seems to be an issue with the version number:
{
"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"
}
}
}
}
}
For more details, please check https://opensearch.org/docs/latest/upgrade-to/upgrade-to/#upgrade-to-opensearch
1 reply
java.util.concurrent.CompletionException: com.datastax.oss.driver.api.core.NoNodeAvailableException: No node was available to execute the query
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]
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]
Did anyone encounter this? If yes, what could be the possible reason
One possible reason of it happening is increase in load. But this error should settle when the load decrease during non peak hours. On the other hand, it's a continuous error and impacting our ingestion into cassandra
hello, it is possible disable cutting of servicename in dependency ui page?
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
I am facing issues from with cassandra3 and zipkin setup while ssl is enables in config.Its doesnt accept javax.net.truststore and javax.net.keystore variables, Any help with Zipkin - > cassandra with ssl setup?? It works well without ssl.
@nitishgoyal13: Did u set up ssl communication with Cassandra?
Hello, I am sorry to keep asking for a review for my PR (openzipkin/zipkin#3384), but I haven't been able to get my PR to the next step (or make any meaningful progress) for a month. (I only got only one LGTM sign from the reviewers. Thanks, Tommy Ludwig.) Could someone help me?
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
Or you can put your traceid into your url :)
/zipkin/traces/{traceId}
zipkin-server use log4j2.
Hi, I deploy zipkin with k8s,
when i use kafka with jaas, Exception thorws like this
wihtout JAVA_OPT env, It works well
What can i do?
4 replies
sudo docker run -d -p 9411:9411 \
-e ES_HOSTS=http://172.30.5.99:3002 \
-e ES_INDEX=tracing \
-e STORAGE_TYPE=elasticsearch \
--name=zipkin_test openzipkin/zipkin
The container does not start, it stays in "starting" mode in portainer, then it stops. are the env-var ES_HOSTS and ES_INDEX supported by default in the image?
2 replies
I'm trying to use zipkin zipkin-cassandra with podman-compose on CentOS 8. The docker-compose-dependencies.yml wants to setup a cron job, but maybe it assumes we've somehow got cron in our container already. Is there an easy way to "fix" this podman-compose wise? Error we get: podman start -a dependencies
Error: unable to start container 8ba0b42f90cb60d00b74fe9d85018b9da16a79fcb3f6bba08b480aaa55ffae20: container_linux.go:380: starting container process caused: exec: "crond -f": executable file not found in $PATH: OCI runtime attempted to invoke a command that was not found
Error: unable to start container 8ba0b42f90cb60d00b74fe9d85018b9da16a79fcb3f6bba08b480aaa55ffae20: container_linux.go:380: starting container process caused: exec: "crond -f": executable file not found in $PATH: OCI runtime attempted to invoke a command that was not found
2 replies