-
Notifications
You must be signed in to change notification settings - Fork 226
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add README for how to use jaeger tracing (#3040)
- Loading branch information
Showing
1 changed file
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
### How to enable jaeger tracing | ||
|
||
If you want to enable jaeger tracing of the porch-server: | ||
|
||
* Apply the [deployment.yaml manifest](deployment.yaml) from this directory | ||
|
||
``` | ||
kubectl apply -f deployment.yaml | ||
``` | ||
|
||
* Add the commented out env var OTEL to the porch-server manifest: | ||
|
||
``` | ||
kubectl edit deployment -n porch-system porch-server | ||
``` | ||
|
||
``` | ||
env: | ||
# Uncomment to enable trace-reporting to jaeger | ||
#- name: OTEL | ||
# value: otel://jaeger-oltp:4317 | ||
``` | ||
|
||
* Port-forward the jaeger http port to your local machine: | ||
|
||
``` | ||
kubectl port-forward -n porch-system service/jaeger-http 16686 | ||
``` | ||
|
||
* Open your browser to the UI on http://localhost:16686 |