Re: KNative Eventing - Traces not showingup at zipkin

[Francesco Guardiani]

> 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 <chand...@gmail.com> 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.

Pods

Logs

[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=http://scl17uri.us.oracle.com:9411/api/v2/spans loggingDebugEnabled=false","logger_name":"dev.knative.eventing.kafka.broker.core.tracing.Tracing","thread_name":"main","level":"INFO","level_value":20000,"backend":"ZIPKIN","sampleRate":1.0,"URL":"http://scl17uri.us.oracle.com:9411/api/v2/spans","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
bugEnabled":false}
...

...

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: http://scl17uri.us.oracle.com:9411/api/v2/spans
     12 kind: ConfigMap
     13 metadata:
     14   annotations:
     15     knative.dev/example-checksum: 4002b4c2
     16     kubectl.kubernetes.io/last-applied-configuration: |
     17       {"apiVersion":"v1","data":{"_example":"################################\n#                              #\n#    EXAMPLE CONFIGURATIO
     18   creationTimestamp: "2021-06-29T16:05:58Z"
     19   labels:
     20     kafka.eventing.knative.dev/release: devel
     21     knative.dev/config-category: eventing
     22     knative.dev/config-propagation: 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?

Chandra

--
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 knative-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/knative-users/1832dc89-b95e-4c0c-a330-e25d65dc6cbcn%40googlegroups.com.

--

Francesco Guardiani

Software Engineer

Red Hat Srl

fgua...@redhat.com   

[Chandrasekhar Rao]

We are experimenting with v0.23 

Thanks

Chandra

[Francesco Guardiani]

Can you try the latest 0.24 release? https://github.com/knative-sandbox/eventing-kafka-broker/releases/tag/v0.24.0

It contains a rework of the tracing support, perhaps it fixes the problem for you.

To view this discussion on the web visit https://groups.google.com/d/msgid/knative-users/9be30fee-d4c4-4dd1-b88f-4484689ddcaen%40googlegroups.com.

[Chandrasekhar Rao]

Hi 

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?

Chandra