Accessing logs

    • 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 . 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”.

    To find the logs sent to from your application in the Kibana UI:

    1. Click Discover on the left side bar.
    2. Choose logstash-* index pattern on the left top.

    To access the request logs (if enabled), enter the following search in Kibana:

    1. _exists_:"httpRequest.requestUrl"

    To access the logs for a configuration:

    • Find the configuration’s name with the following command:
    1. kubectl get configurations
    • Replace and enter the following search query in Kibana:

    To access logs for a revision:

    • Find the revision’s name with the following command:
      • Replace <REVISION_NAME> and enter the following search query in Kibana:

      See Accessing Traces page for details.

      Stackdriver

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