Easy jaeger/opentracing integration in GDK
The GitLab application is now instrumented with OpenTracing compatible instrumentation.
It is relatively easy to obtain distributed tracing information in the GDK, through a two step process:
- export the
GITLAB_TRACING
connection string - start the Jaeger all-in-one docker container
See https://www.youtube.com/watch?v=8WUZLZIMpp4 for more details...
This issue is to discuss if and how to make this 1) easier 2) more accessible and 3) more visible to GitLab developers.
Some questions:
- Is the current process easy enough? (Probably not)
- Is opentracing support obvious to new developers? (Probably not)
- Should we enable opentracing and jaeger by default in GDK?
- To improve the developer-UX of opentracing, should we integrate opentracing into the performance bar (for example)?
Thinking out loud: I think it would be great if we could allow developers to opt into opentracing (eg: through a configuration?). In this setup, GITLAB_TRACING
would be auto-configured and the Jaeger all-in-one docker container would start as part of gdk run db
.
Edited by Andrew Newdigate