Monitoring migrated workloads

You can view logs and metrics from your migrated workloads in the Google Cloud Console. You can also view logs from the command line with kubectl.

Viewing metrics on the GKE console

The GKE console and Stackdriver provide a suite of tools to monitor your containers. To get started:

  1. Open GKE Workloads
  2. Click on the name of the workload you would like to monitor.

From here, you can see details about this workload, including aggregate graphs of performance across all of the pods.

Viewing logs in Stackdriver Logging

Once you enable Stackdriver, you can view workload logs in the Stackdriver user interface.

You can use Stackdriver to view logs for the following aspects of your migration:

  • Logs written to stdout by processes launched by init. This is done by default.
  • The content of var/log/syslog.
  • Optionally, application logs written to the file system.
  • For more on file system logs written to Stackdriver, see Configuring logging to Stackdriver Logging.

You can view system logs that are in Stackdriver from the GCP Console. To do so:

  1. Open GKE Workloads.
  2. Find your workload and click on its Name. The Deployment Details page appears.
  3. Find the row labeled Logs and click on Container logs.

This loads Stackdriver, showing logs for this workload only.

Container logs in Stackdriver

Viewing logs in kubectl

You can use kubectl to retrieve logs from a running container. You can also monitor the progress of export from short-term to long-term storage.

To view the logs for a pod:

  1. Find the name of your pod from the output of kubectl get pods. In the example below, the pod's name is suitecrm-app-0.

    kubectl get pods
    NAME                       READY     STATUS    RESTARTS   AGE
    csi-disk-controller-0   3/3       Running   4          4d
    csi-disk-node-5t922     3/3       Running   3          4d
    csi-disk-node-5tdcp     3/3       Running   3          4d
    csi-disk-node-86c2t     3/3       Running   3          4d
    csi-disk-node-8785n     3/3       Running   3          4d
    suitecrm-app-0       1/1       Running   0          17h
  2. View the logs from your pod with kubectl logs.

    kubectl logs [POD_NAME]
    I0529 07:01:26.000000    12] [suitecrm-app-0] - Auto-detected template: centos
    D0529 07:01:26.000000    12] [util] - SHELL OUTPUT: UNIT FILE                                     STATE
    D0529 07:01:26.000000    12] [util] - SHELL OUTPUT: adservice.service                             enabled

The pod's recent logs are displayed.

For more information on logging and Kubernetes, see the Kubernetes Logging documentation.