#1324 fix: logs exposed by istio-telemetry and not by istio-mixer for now. (#1405)

This commit is contained in:
olegchorny 2018-06-01 16:34:35 +03:00 committed by Martin Taillefer
parent 2df0afb955
commit 5f9dc71b7e
1 changed files with 2 additions and 2 deletions

View File

@ -163,11 +163,11 @@ as the example application throughout this task.
1. Verify that the logs stream has been created and is being populated for
requests.
In a Kubernetes environment, search through the logs for the Mixer pod as
In a Kubernetes environment, search through the logs for the istio-telemetry pod as
follows:
```command-output-as-json
$ kubectl -n istio-system logs $(kubectl -n istio-system get pods -l istio=mixer -o jsonpath='{.items[0].metadata.name}') mixer | grep \"instance\":\"newlog.logentry.istio-system\"
$ kubectl -n istio-system logs $(kubectl -n istio-system get pods -l istio-mixer-type=telemetry -o jsonpath='{.items[0].metadata.name}') mixer | grep \"instance\":\"newlog.logentry.istio-system\"
{"level":"warn","ts":"2017-09-21T04:33:31.249Z","instance":"newlog.logentry.istio-system","destination":"details","latency":"6.848ms","responseCode":200,"responseSize":178,"source":"productpage","user":"unknown"}
{"level":"warn","ts":"2017-09-21T04:33:31.291Z","instance":"newlog.logentry.istio-system","destination":"ratings","latency":"6.753ms","responseCode":200,"responseSize":48,"source":"reviews","user":"unknown"}
{"level":"warn","ts":"2017-09-21T04:33:31.263Z","instance":"newlog.logentry.istio-system","destination":"reviews","latency":"39.848ms","responseCode":200,"responseSize":379,"source":"productpage","user":"unknown"}