Grafana dashboards for containers in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Grafana used for in container monitoring?

Grafana is used to visualize and analyze metrics collected from containers, helping you understand container performance and health through dashboards.

beginner

Which data source is commonly used with Grafana to monitor Docker containers?

Prometheus is commonly used as a data source for Grafana to collect and store container metrics.

intermediate

How do you add a Docker container metrics data source in Grafana?

You add Prometheus as a data source in Grafana, then configure Prometheus to scrape metrics from Docker or container exporters.

intermediate

What is a common exporter used to expose Docker container metrics to Prometheus?

cAdvisor is a common exporter that collects container metrics and exposes them for Prometheus to scrape.

beginner

Name one key metric you can monitor on a Grafana dashboard for containers.

CPU usage, memory usage, network I/O, and disk I/O are key metrics often monitored on Grafana dashboards for containers.

Which tool visualizes container metrics in dashboards?

A Docker CLI

B Grafana

C Git

D Kubernetes

Grafana is the tool used to create dashboards for visualizing container metrics.

What data source does Grafana commonly use for container metrics?

A MySQL

B Elasticsearch

C Prometheus

D InfluxDB

Prometheus is widely used to collect and store container metrics for Grafana dashboards.

Which exporter collects Docker container metrics for Prometheus?

A cAdvisor

B Node Exporter

C Fluentd

D Telegraf

cAdvisor collects container metrics and exposes them to Prometheus.

What metric would you NOT typically monitor on a container dashboard?

A CPU usage

B Memory usage

C Disk I/O

D Email inbox size

Email inbox size is unrelated to container performance metrics.

How do you connect Prometheus to Grafana?

A Add Prometheus as a data source in Grafana

B Install Prometheus inside Grafana

C Run Grafana inside Prometheus

D Use Docker CLI to link them

You add Prometheus as a data source in Grafana to visualize its collected metrics.

Explain how Grafana, Prometheus, and cAdvisor work together to monitor Docker containers.

Think about the flow of data from container to dashboard.

Describe the steps to set up a Grafana dashboard for monitoring Docker containers.

Focus on installation, configuration, and visualization steps.

Practice

1. What is the primary purpose of using Grafana dashboards for Docker containers?

easy

A. To write Dockerfiles automatically

B. To visually monitor container health and performance metrics

C. To build Docker images faster

D. To deploy containers without configuration

Solution

1. Step 1: Understand Grafana's role

   Grafana is a tool designed to visualize data, especially metrics and logs.

2. Step 2: Connect Grafana to container metrics

   When connected to data sources like Prometheus, Grafana shows container health and performance visually.

3. Final Answer:

   To visually monitor container health and performance metrics -> Option B

4. Quick Check:

   Grafana = Visual monitoring [OK]

Hint: Grafana = Visual dashboards for metrics [OK]

Common Mistakes:

• Confusing Grafana with image building tools
• Thinking Grafana deploys containers
• Assuming Grafana writes Dockerfiles

2. Which Docker command correctly runs Grafana exposing it on port 3000?

easy

A. docker run -d -p 80:3000 grafana/grafana

B. docker run -d -p 8080:3000 grafana/grafana

C. docker run -d -p 3000:8080 grafana/grafana

D. docker run -d -p 3000:3000 grafana/grafana

Solution

1. Step 1: Identify Grafana default port

   Grafana listens on port 3000 inside the container.

2. Step 2: Map host port 3000 to container port 3000

   The correct syntax is -p hostPort:containerPort, so -p 3000:3000 exposes Grafana on host port 3000.

3. Final Answer:

   docker run -d -p 3000:3000 grafana/grafana -> Option D

4. Quick Check:

   Port mapping = host:container [OK]

Hint: Map host port 3000 to container port 3000 [OK]

Common Mistakes:

• Swapping host and container ports
• Using wrong ports like 8080 or 80
• Not running container in detached mode

3. Given this Docker command, what will happen when you access http://localhost:3000?

docker run -d -p 3000:3000 grafana/grafana

medium

A. You will see the Docker container logs

B. You will get a 404 Not Found error

C. You will see the Grafana login page

D. The browser will fail to connect

Solution

1. Step 1: Understand port mapping

   Port 3000 on localhost is forwarded to Grafana's port 3000 inside the container.

2. Step 2: Accessing localhost:3000 loads Grafana UI

   Grafana serves its web interface on port 3000, so the login page appears.

3. Final Answer:

   You will see the Grafana login page -> Option C

4. Quick Check:

   Port 3000 mapped = Grafana UI loads [OK]

Hint: Port 3000 access shows Grafana login [OK]

Common Mistakes:

• Expecting error pages instead of UI
• Confusing logs with web interface
• Assuming no connection due to missing config

4. You ran Grafana with docker run -d -p 3000:3000 grafana/grafana but cannot access the dashboard at http://localhost:3000. What is a likely cause?

medium

A. Grafana container is not running or crashed

B. You used the wrong image name

C. Port 3000 is not exposed inside the container

D. Docker daemon is not installed

Solution

1. Step 1: Check container status

   If the container stopped or crashed, the port won't be accessible.

2. Step 2: Verify container is running

   Use docker ps to confirm Grafana container is active.

3. Final Answer:

   Grafana container is not running or crashed -> Option A

4. Quick Check:

   Container running = Dashboard accessible [OK]

Hint: Check container status with docker ps [OK]

Common Mistakes:

• Assuming wrong image name without checking
• Thinking port exposure inside container is missing
• Ignoring Docker daemon status

5. You want to monitor multiple Docker containers' CPU and memory usage in Grafana. Which setup step is essential before creating dashboards?

hard

A. Connect Grafana to a metrics data source like Prometheus collecting container stats

B. Install Grafana plugins inside each container

C. Run Grafana with extra CPU and memory limits

D. Expose all container ports to the host

Solution

1. Step 1: Understand Grafana data source role

   Grafana itself does not collect metrics; it visualizes data from sources like Prometheus.

2. Step 2: Set up Prometheus to scrape container metrics

   Prometheus collects CPU and memory stats from Docker containers and provides data to Grafana.

3. Step 3: Connect Grafana to Prometheus

   Configure Grafana to use Prometheus as a data source to build dashboards.

4. Final Answer:

   Connect Grafana to a metrics data source like Prometheus collecting container stats -> Option A

5. Quick Check:

   Data source connection = Dashboard data [OK]

Hint: Grafana needs data source like Prometheus first [OK]

Common Mistakes:

• Thinking Grafana collects metrics alone
• Installing plugins inside containers unnecessarily
• Exposing all ports without reason