GKE monitoring and logging in GCP - Step-by-Step Execution

Process Flow - GKE monitoring and logging

Deploy GKE Cluster

↓

Enable Monitoring & Logging

↓

Collect Metrics & Logs

↓

Send Data to Cloud Operations

↓

View Dashboards & Alerts

↓

Analyze & Troubleshoot

This flow shows how a GKE cluster is set up with monitoring and logging enabled, data is collected and sent to Cloud Operations, and then viewed for analysis.

Execution Sample

GCP

gcloud container clusters create my-cluster \
  --zone us-central1-a \
  --enable-stackdriver-kubernetes

gcloud container clusters get-credentials my-cluster --zone us-central1-a

kubectl get pods --namespace=kube-system

Creates a GKE cluster with monitoring enabled, authenticates kubectl to the cluster, and checks system pods running for logging agents.

Process Table

Step	Command/Action	Result/Output	System State Change
1	gcloud container clusters create my-cluster --zone us-central1-a --enable-stackdriver-kubernetes	Cluster 'my-cluster' created with monitoring enabled	GKE cluster created with Stackdriver monitoring and logging agents installed
2	gcloud container clusters get-credentials my-cluster --zone us-central1-a kubectl get pods --namespace=kube-system	Credentials updated. Lists pods including 'stackdriver-agent' and 'fluentd-gcp-scaler'	kubectl authenticated; Monitoring and logging agents are running in the cluster
3	Generate workload (e.g., deploy app)	App pods start running and generate logs and metrics	Logs and metrics start flowing to Cloud Operations
4	Go to Google Cloud Console > Monitoring	View cluster metrics dashboards	Metrics visualized for CPU, memory, network, etc.
5	Go to Google Cloud Console > Logging	View logs from cluster pods and system components	Logs searchable and filterable for troubleshooting
6	Set alert policies in Monitoring	Alerts trigger on defined conditions	Proactive notifications for cluster health
7	Analyze dashboards and logs	Identify issues or performance bottlenecks	Improved cluster reliability and debugging
8	Exit	Monitoring and logging setup complete	System continuously collects and displays data

💡 Monitoring and logging agents are running; data flows to Cloud Operations for ongoing analysis

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Cluster State	None	Created with monitoring enabled	Agents running	Workload generating data	Data flowing to Cloud Operations
Pods in kube-system	None	Created	stackdriver-agent and fluentd-gcp-scaler running	No change	No change
Metrics Data	None	None	None	Generated by workload	Available in Monitoring
Logs Data	None	None	None	Generated by workload and system	Available in Logging

Key Moments - 3 Insights

Why do we see 'stackdriver-agent' pods in the kube-system namespace?

These pods are the monitoring and logging agents installed automatically when creating the cluster with --enable-stackdriver-kubernetes, as shown in execution_table step 2.

How does enabling monitoring affect the cluster workload?

Enabling monitoring adds agents that collect metrics and logs without changing the workload itself, but workload pods generate data that these agents send to Cloud Operations (see steps 3 and 4).

What happens if we don't enable monitoring during cluster creation?

No monitoring or logging agents are installed automatically, so metrics and logs won't be collected or visible in Cloud Operations unless manually configured (not shown in the execution table).

Visual Quiz - 3 Questions

Look at the execution table at step 2, which pods indicate monitoring and logging are active?

A stackdriver-agent and fluentd-gcp-scaler

B kube-dns and coredns

C nginx-ingress-controller

D etcd and kube-apiserver

💡 Hint

Check the 'Result/Output' column at step 2 in the execution table.

At which step does the cluster start sending metrics and logs to Cloud Operations?

A Step 1

B Step 3

C Step 5

D Step 7

💡 Hint

Look for when workload pods generate data in the execution table.

If you remove the --enable-stackdriver-kubernetes-engine flag during cluster creation, what changes in the execution table?

A Step 4 dashboards will show more metrics

B Step 6 alerts will trigger more often

C Step 2 will not show stackdriver-agent pods running

D Step 3 workload pods will not start

💡 Hint

Refer to the presence of monitoring agents in step 2.

Concept Snapshot

GKE monitoring and logging setup:
- Create cluster with --enable-stackdriver-kubernetes
- Agents run in kube-system namespace
- Metrics and logs collected from workloads
- Data sent to Cloud Operations
- View dashboards and logs in Google Cloud Console
- Set alerts for proactive monitoring

Full Transcript

This visual execution shows how to enable monitoring and logging in a Google Kubernetes Engine cluster. First, you create the cluster with the flag --enable-stackdriver-kubernetes, which installs monitoring and logging agents automatically. Then, you verify these agents by listing pods in the kube-system namespace. When you deploy workloads, they generate metrics and logs that the agents collect and send to Google Cloud Operations. You can then view these metrics in Monitoring dashboards and logs in Logging. Alerts can be set up to notify you of issues. This setup helps you keep your cluster healthy and troubleshoot problems efficiently.