docs/accessing-logs.md at ec3b20653deedf90f7e29b83ee2d6e62c07e7199

3.7 KiB

Raw Blame History

title	weight	type
Accessing logs	5	docs

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:
```
kubectl proxy
```
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:

Click Discover on the left side bar.
Choose logstash-* index pattern on the left top.
Input 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:

_exists_:"httpRequest.requestUrl"

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

Replace <CONFIGURATION_NAME> and enter the following search query in Kibana:

kubernetes.labels.serving_knative_dev\/configuration: <CONFIGURATION_NAME>

To access logs for a revision:

Find the revision's name with the following command:

kubectl get revisions

Replace <REVISION_NAME> and enter the following search query in Kibana:

kubernetes.labels.serving_knative_dev\/revision: <REVISION_NAME>

Accessing end to end request traces

See Accessing Traces page for details.

Stackdriver

Go to the GCP Console logging page for your GCP project, which stores your logs via Stackdriver.

3.7 KiB Raw Blame History