We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.
If you have not yet installed the logging and monitoring components, go through the installation instructions to set up the necessary components first.
Kibana and Elasticsearch
To open the Kibana UI (the visualization tool for Elasticsearch), start a local proxy with the following command:
This command starts a local proxy of Kibana on port 8001. For security reasons, the Kibana UI is exposed only within the cluster.
Navigate to the Kibana UI. It might take a couple of minutes for the proxy to work.
The Discover tab of the Kibana UI looks like this:
You can change the time frame of logs Kibana displays in the upper right corner of the screen. The main search bar is across the top of the Discover page.
As more logs are ingested, new fields will be discovered. To have them indexed, go to “Management” > “Index Patterns” > Refresh button (on top right) > “Refresh fields”.
Accessing stdout/stderr logs
To find the logs sent to
stdout/stderr from your application in the Kibana UI:
Discoveron the left side bar.
logstash-*index pattern on the left top.
tag: kubernetes*in the top search bar then search.
Accessing request logs
To access the request logs (if enabled), enter the following search in Kibana:
Request logs contain customized details about requests served by the revision. Below is a sample request log:
@timestamp July 10th 2018, 10:09:28.000 kubernetes.labels.serving_knative_dev/configuration helloworld-go kubernetes.labels.serving_knative_dev/revision helloworld-go-6vf4x kubernetes.labels.serving_knative_dev/service helloworld-go httpRequest.protocol HTTP/1.1 httpRequest.referer httpRequest.remoteIp 10.32.0.2:46866 httpRequest.requestMethod GET httpRequest.requestSize 0 httpRequest.requestUrl / httpRequest.responseSize 20 httpRequest.serverIp 10.32.1.36 httpRequest.status 200 httpRequest.userAgent curl/7.60.0 traceId 0def9abf835ad90e9d824f7a492e2dcb
Accessing configuration and revision logs
To access the logs for a configuration:
- Find the configuration’s name with the following command:
kubectl get configurations
<CONFIGURATION_NAME>and enter the following search query in Kibana:
To access logs for a revision:
- Find the revision’s name with the following command:
kubectl get revisions
<REVISION_NAME>and enter the following search query in Kibana:
Accessing end to end request traces
See Accessing Traces page for details.
Go to the GCP Console logging page for your GCP project, which stores your logs via Stackdriver.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.