If Jaeger is configured (using the
useJaeger site configuration)
property, every HTTP response will include an
X-Trace header with a link to the trace for that
request. Inspecting the spans and logs attached to the trace will help identify the problematic
service or dependency.
If you are using the single Docker container or Docker Compose deployment method for Sourcegraph, refer to the official Jaeger documentation for guidance. Note that you have two options:
If you are using Kubernetes, you can refer to these docs on how to run Jaeger in the Sourcegraph cluster.
If you are using the single Docker container or Docker Compose deployment, you’ll need to make the Jaeger UI (jaeger-query) accessible to site admins.
If you are using Kubernetes and have followed the recommended docs above to run Jaeger in the Sourcegraph cluster, you can access the the Jaeger UI with port-forwarding at http://localhost:16686/:
kubectl port-forward svc/jaeger-query 16686