kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update docs for jaeger-query host binary, prow jobs, and screenshot

This commit is contained in:
Peter Rifel 2024-01-04 18:36:27 -06:00
parent 8000ce5718
commit 23360253f3
No known key found for this signature in database
2 changed files with 36 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/img/jaeger-query.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 MiB

37
docs/opentelemetry.md
View File

@ -12,12 +12,47 @@ To try this out:
You should now see that the /tmp/trace file is created.
Then we have an experimental tool to serve the trace file to jaeger:
Then we have an experimental tool to serve the trace file to jaeger. First ensure `jaeger-query` is in your PATH, available [here](https://www.jaegertracing.io/download/#binaries)
```
cd tools/otel/traceserver
go run . --src /tmp/trace --run jaeger
```
Alternatively you can use the jaeger docker image with:
```
go run . --src /tmp/trace --run docker-jaeger
```
This will open your local jaeger-query's frontend in a web browser:
![Jaeger UI](./img/jaeger-query.png)
Not everything is instrumented yet, and not all the traces are fully joined up (we need to thread more contexts through more methods),
but you should be able to start to explore the operations that we run and their performance.
## Prow Jobs
Tracing is enabled in the kops prow jobs. `.otel` files are created during job execution and included as job artifacts in the `otlp` subdirectory.
Example:
```
https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/kops/16204/presubmit-kops-aws-scale-amazonvpc-using-cl2/1742962895290896384/artifacts/otlp/
```
Download these files to a local directory, either with `gsutil` or through a web browser
```
mkdir /tmp/job-traces
gsutil cp -r gs://kubernetes-jenkins/pr-logs/pull/kops/16204/presubmit-kops-aws-scale-amazonvpc-using-cl2/1742962895290896384/artifacts/otlp/ /tmp/job-traces
```
Then run the trace server as normal:
```sh
cd tools/otel/traceserver
go run . --src /tmp/traces --run jaeger
```