Section 1 - Instruction

You've learned about the three pillars of observability: logs, metrics, and traces. Now let's practice using each one to diagnose issues in your cloud-native, containerized pipelines.

Different problems require different observability tools.

Engagement Message

Ready to become a pipeline detective?

Section 2 - Practice

Type

Multiple Choice

Practice Question

Your containerized data pipeline suddenly starts taking 3x longer to process the same amount of data. Which observability tool would help you find the bottleneck?

A. Logs to see error messages B. Metrics to identify performance trends C. Traces to see where time is spent D. Alerts to notify when it happens again

Suggested Answers

  • A
  • B
  • C - Correct
  • D
Section 3 - Practice

Type

Sort Into Boxes

Practice Question

Sort these observability signals into the correct categories:

Labels

  • First Box Label: Logs
  • Second Box Label: Metrics

First Box Items

  • Error messages
  • Failed connections
  • API responses

Second Box Items

  • CPU usage
  • Processing time
  • Memory consumption
Section 4 - Practice

Type

Swipe Left or Right

Practice Question

Let's practice matching investigation approaches to problem scenarios. Swipe each scenario to the best observability approach:

Labels

  • Left Label: Use Logs
  • Right Label: Use Metrics
Sign up
Join the 1M+ learners on CodeSignal
Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal