hypertrace icon indicating copy to clipboard operation
hypertrace copied to clipboard
verified publisher icon hypertrace

Provide a way to upload/download a trace to debug it

Open jcchavezs opened this issue 5 years ago • 3 comments

Currently it is really hard to debug a trace because we don't know what is the data being represented in the UI. Issues like discrepancy of data or missing fields (e.g. https://github.com/hypertrace/hypertrace-ui/issues/283) can be debugged in this way, otherwise hard to.

Ideally we should use a format that can be: downloaded over http, uploaded over http and consumed easily (e.g. http). Zipkin format fits in all this as we can ingest zipkin data. It will also safe the need to build (or use) tools like https://github.com/jcchavezs/jaeger2zipkin

Some examples on how debugging will be better:

  • https://hypertrace.slack.com/archives/C0174CTSF5Y/p1603761323031000
  • https://gist.github.com/jcchavezs/88c4c687e2e82e23bd5cee162f0b5914#file-0readme-md

Ping @kotharironak @jake-bassett @JBAhire @adriancole @buchi-busireddy

jcchavezs avatar Oct 28 '20 06:10 jcchavezs

Agree on this. It will surely make things easier!

JBAhire avatar Oct 28 '20 06:10 JBAhire

@buchi-busireddy you were suggesting something on this? Can you provide more details?

kotharironak avatar Oct 29 '20 04:10 kotharironak

@jcchavezs can this issue be moved to hypertrace as this is a feature request?

kotharironak avatar Oct 29 '20 04:10 kotharironak