Re: KNative Eventing - Traces not showingup at zipkin

Skip to first unread message

Francesco Guardiani

Jul 7, 2021, 1:50:20 AMJul 7
to Chandrasekhar Rao, Knative Users
> or this version of knative does not support it?

Which version are you using?

Also can you try to enable debug: "true"? It should enable to show traces in the log. Please note that eventing-kafka-broker tracing support does not generate traces, but just propagates and publish them

On Tue, Jul 6, 2021 at 6:45 PM Chandrasekhar Rao <> wrote:
Hey folks,
i have the following config map added to the knative service and have zipkin running on that same node outside the cluster.
[ctrao@slc17uri ~]$ kubectl logs -f kafka-broker-dispatcher-78bdb4bbf9-g7kzg -n knative-eventing
{"@timestamp":"2021-07-06T15:23:07.613Z","@version":"1","message":"Registering tracing configurations backend=ZIPKIN sampleRate=1.0 URL= loggingDebugEnabled=false","logger_name":"","thread_name":"main","level":"INFO","level_value":20000,"backend":"ZIPKIN","sampleRate":1.0,"URL":"","loggingDeJul 06, 2021 3:23:08 PM com.fasterxml.jackson.databind.ext.Java7Handlers <clinit>
WARNING: Unable to load JDK7 types (java.nio.file.Path): no Java7 type support added

I do not see the traces come out to zipkin. Is there any way to troubleshoot this? I cannot loging into pods

      1 # Please edit the object below. Lines beginning with a '#' will be ignored,
      2 # and an empty file will abort the edit. If an error occurs while saving this file will be
      3 # reopened with the relevant failures.
      4 #
      5 apiVersion: v1
      6 data:
      7   backend: zipkin
      8   debug: "false"
      9   enable: "true"
     10   sample-rate: "1"
     11   zipkin-endpoint:
     12 kind: ConfigMap
     13 metadata:
     14   annotations:
     15 4002b4c2
     16 |
     17       {"apiVersion":"v1","data":{"_example":"################################\n#                              #\n#    EXAMPLE CONFIGURATIO
     18   creationTimestamp: "2021-06-29T16:05:58Z"
     19   labels:
     20 devel
     21 eventing
     22 original
     23   name: config-tracing
     24   namespace: knative-eventing
     25   resourceVersion: "10060394"
     26   uid: 388e36e3-8b52-4405-acac-3242b39822ee

Curios if I have something missing etc... or this version of knative does not support it?


You received this message because you are subscribed to the Google Groups "Knative Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit


Francesco Guardiani

Software Engineer

Red Hat Srl   

Chandrasekhar Rao

Jul 7, 2021, 11:28:35 AMJul 7
to Knative Users
We are experimenting with v0.23 



Francesco Guardiani

Jul 7, 2021, 12:49:54 PMJul 7
to Chandrasekhar Rao, Knative Users
It contains a rework of the tracing support, perhaps it fixes the problem for you.

Chandrasekhar Rao

Jul 8, 2021, 3:05:00 PMJul 8
to Knative Users

I have tried the same with V24 this morning , and get the same results - I do not see anything at the jaeger collector...
Every time I change the config I am even doing a rolling restart of all pods in this namespace...
"kubectl rollout restart deployment -n knative-eventing kafka-broker-dispatcher kafka-broker-receiver kafka-ch-controller kafka-controller kafka-webhook kafka-webhook-eventing eventing-controller eventing-webhook"

Did any one get eventing tracing working in any other way?

Reply all
Reply to author
0 new messages