Copy edits to accessing-traces.md (#174)

This commit is contained in:
Peter Delaney 2018-07-18 10:36:31 -07:00 committed by Google Prow Robot
parent 6f3490b28d
commit 0401c1ada6
1 changed files with 16 additions and 13 deletions

View File

@ -1,21 +1,24 @@
# Accessing request traces # Accessing request traces
If logging and monitoring components are not installed yet, go through the If you have not yet installed the logging and monitoring components, go through the
[installation instructions](./installing-logging-metrics-traces.md) to setup the [installation instructions](./installing-logging-metrics-traces.md) to set up the
necessary components first. necessary components.
To open the Zipkin UI (the visualization tool for request traces), enter the following command: In order to access request traces, you use the Zipkin visualization tool.
```shell 1. To open the Zipkin UI, enter the following command:
kubectl proxy
```
This starts a local proxy of Zipkin on port 8001. The Zipkin UI is only exposed within ```shell
the cluster for security reasons. kubectl proxy
```
Navigate to the [Zipkin UI](http://localhost:8001/api/v1/namespaces/istio-system/services/zipkin:9411/proxy/zipkin/). This command starts a local proxy of Zipkin on port 8001. For security reasons, the
Click on "Find Traces" to see the latest traces. You can search for a trace ID Zipkin UI is exposed only within the cluster.
or look at traces of a specific application. Click on a trace to see a detailed
view of a specific call. 1. Navigate to the [Zipkin UI](http://localhost:8001/api/v1/namespaces/istio-system/services/zipkin:9411/proxy/zipkin/).
1. Click "Find Traces" to see the latest traces. You can search for a trace ID
or look at traces of a specific application. Click on a trace to see a detailed
view of a specific call.
<!--TODO: Consider adding a video here. --> <!--TODO: Consider adding a video here. -->