# Query traces not appearing on Jaeger

**URL:** <https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183>\
**Category:** Dgraph\
**Created:** [January 18, 2023, 3:17am UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183 "2023-01-18T03:17:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cscetbon](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/cscetbon/32/10100_2.png) [@cscetbon](https://discuss.dgraph.io/u/cscetbon)\
**Post date:** [January 18, 2023, 3:17am UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183/1 "2023-01-18T03:17:43Z")

</div>

Continuing the discussion from [Tracing - Deploy](http://discuss.hypermode.com/t/tracing-deploy/9810/2):

I have deployed a cluster with Jaeger enabled and its ratio set to 100%. I’m trying to trace queries but I see nothing in Jaeger. I can see them in ZPages though but I wonder why they can’t be seen in Jaeger. I see otrace being used in both cases but I’m not sure how something ends in ZPages but not in Jaeger. Is there any good explanation ? any reason why it’s not collected by Jaeger

Thanks

---

<div class="post-metadata">

**Author:** ![matthewmcneely](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/matthewmcneely/32/4774_2.png) [@matthewmcneely](https://discuss.dgraph.io/u/matthewmcneely)\
**Post date:** [January 18, 2023, 8:07pm UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183/2 "2023-01-18T20:07:42Z")

</div>

Hiya @cscetbon,

Can you compare your setup to this repo (checkout the docker-compose file): [GitHub - matthewmcneely/dgraph-v21.03-sandbox at issue/list-compaction-stale-transaction](https://github.com/matthewmcneely/dgraph-v21.03-sandbox/tree/issue/list-compaction-stale-transaction) ?

---

<div class="post-metadata">

**Author:** ![cscetbon](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/cscetbon/32/10100_2.png) [@cscetbon](https://discuss.dgraph.io/u/cscetbon)\
**Post date:** [January 19, 2023, 4:25am UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183/3 "2023-01-19T04:25:31Z")

</div>

For some reason it started to appear as expected 🤷‍♂️

 ![Screenshot 2023-01-18 at 11.18.12 PM](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/b/bb76889257ff3b92404e46749667fbb71889b843.png)

So I guess I’m good. One question though, any idea why I see many \u0000 characters in the schema I’m using ?

 ![Screenshot 2023-01-18 at 11.19.50 PM](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/6/68d241cb752fa890cf5a4785b3d74dff77ae0836.png)

You can see my cluster’s state at [https://pastebin.com/raw/ufdukkbn](https://pastebin.com/raw/ufdukkbn) to see what I’m talking about, if you look at all predicates.

---

<div class="post-metadata">

**Author:** ![matthewmcneely](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/matthewmcneely/32/4774_2.png) [@matthewmcneely](https://discuss.dgraph.io/u/matthewmcneely)\
**Post date:** [January 19, 2023, 2:55pm UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183/4 "2023-01-19T14:55:09Z")

</div>

It has to do with how they’re encoded on disk. There’s a PR in the pipeline to address it: [BREAKING: fix json marshal unmarshal for namespace \> 127 (#7810,#7838,#8091) #8599 by harshil-goel · Pull Request #8602 · dgraph-io/dgraph · GitHub](https://github.com/dgraph-io/dgraph/pull/8602)

---

<div class="post-metadata">

**Author:** ![cscetbon](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/cscetbon/32/10100_2.png) [@cscetbon](https://discuss.dgraph.io/u/cscetbon)\
**Post date:** [January 22, 2023, 5:57pm UTC](https://discuss.dgraph.io/t/query-traces-not-appearing-on-jaeger/18183/5 "2023-01-22T17:57:36Z")

</div>

Thank you @matthewmcneely I’m gonna subscribe to that PR then and as soon as there is an image I can try it and see for myself if it’s actually changing this. UTF-8 characters should load better
