System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) · 강의

현대적인 로그 형식 이해

구조화된 로깅과 JSON과 같은 일반적인 형식을 배웁니다. 구조화된 로그가 일반 텍스트보다 기계 파싱과 분석에 더 적합한 이유를 이해합니다.

현대적인 로그 형식 이해은(는) CoddyKit의 무료 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

What are Application Logs?

Imagine your application as a busy worker. How do you know what it's doing? That's where logs come in!

Logs are like a diary for your software. They record events, operations, and status messages as your application runs. They tell you:

When something happened
What action was performed
If an error occurred

These records are crucial for debugging, monitoring performance, and understanding system behavior.

The Traditional Way: Plain Text

Historically, logs were often simple lines of text. Each event was written as a human-readable string.

For example, a login event might look like this:

2023-10-27 10:30:00 INFO User 'alice' logged in from IP 192.168.1.100

This format is straightforward and easy for a human to read when looking at a few lines.

Plain Text: Hard for Machines

While plain text logs are human-friendly at a glance, they pose a big challenge for computers.

To find all logins from 'alice' or count errors from a specific IP address, a machine would need to:

Guess the date format
Extract the log level ('INFO')
Parse the username ('alice')
Identify the IP address

This process, called parsing, is complex and prone to errors because there's no fixed structure.

Hello, Structured Logging!

This is where structured logging comes to the rescue! It's a modern approach that outputs log data in a consistent, machine-readable format.

Instead of free-form text, each log entry is an object with clearly defined fields (like 'timestamp', 'level', 'user_id', 'message').

Think of it like organizing your notes into a spreadsheet instead of a jumbled notebook. Each piece of information has its own column.

JSON: Your Log's New Structure

The most popular format for structured logging today is JSON (JavaScript Object Notation).

JSON is lightweight, human-readable, and incredibly easy for machines to parse. It represents data as key-value pairs.

Here's how our 'alice' login event might look as a JSON log:

{"timestamp": "2023-10-27T10:30:00Z", "level": "INFO", "message": "User logged in", "user": "alice", "ip_address": "192.168.1.100"}

The Power of Structured Logs

Using structured formats like JSON unlocks powerful capabilities:

Easier Machine Parsing: Computers can directly read and understand each data field.
Efficient Searching: Quickly find logs where user="alice" or level="ERROR".
Better Analysis: Aggregate data, count events, and build dashboards based on specific fields.
No More Guessing: No need for complex regular expressions to extract data, reducing errors.

This transforms logs from simple text files into rich, queryable data.

Example: Outputting a JSON Log

Here's a simple Java example demonstrating how you might output a structured log in JSON format. In real applications, you'd use a logging library to handle this.

Try running it to see the structured output!

public class StructuredLogger {
  public static void main(String[] args) {
    // This is a simplified way to output a JSON log string.
    // Real-world apps use dedicated logging libraries for this.
    String jsonLog = "{\"timestamp\": \"2023-10-27T10:30:00Z\", \"level\": \"INFO\", \"message\": \"User logged in successfully\", \"user_id\": 123, \"ip_address\": \"192.168.1.100\"}";
    System.out.println(jsonLog);
  }
}

Inside a JSON Log Object

Let's break down the JSON log from the previous example:

{"timestamp": "2023-10-27T10:30:00Z", "level": "INFO", "message": "User logged in successfully", "user_id": 123, "ip_address": "192.168.1.100"}

Each piece of information is a key-value pair.
"timestamp" is the key, "2023-10-27T10:30:00Z" is its value.
"level" is the key, "INFO" is its value.

This explicit labeling makes every detail instantly accessible to machines.

Essential Fields in Structured Logs

While you can add any relevant data, some fields are commonly found and highly useful in structured logs:

timestamp: The exact time the event occurred (often in ISO 8601 format).
level: The severity of the log (e.g., DEBUG, INFO, WARN, ERROR, FATAL).
message: A human-readable description of the event.
service: The name of the application or service generating the log.
transaction_id: A unique ID to link related events across different services.
user_id: The ID of the user involved in the event.

Quick Check: Why Structured Logs?

You've learned about the differences between plain text and structured logs. Think about the key benefits.

Recap: Logs Get Organized!

Congratulations! You've taken a crucial step in understanding modern application logging.

We saw that traditional plain text logs are simple but hard for computers to analyze.
Structured logging provides a consistent, machine-readable format for log data.
JSON is the most popular structured format, using key-value pairs.
Structured logs enable powerful searching, filtering, and automated analysis, making your logs far more valuable.

Next, we'll explore how these structured logs are collected and managed in centralized systems!

자주 묻는 질문

“현대적인 로그 형식 이해” 강의는 무료인가요?

네 — “현대적인 로그 형식 이해” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의 전체를 잠금 해제할 수 있습니다. System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의에는 총 4개의 강의가 포함되어 있습니다.

“현대적인 로그 형식 이해”에서 뭘 배우나요?

구조화된 로깅과 JSON과 같은 일반적인 형식을 배웁니다. 구조화된 로그가 일반 텍스트보다 기계 파싱과 분석에 더 적합한 이유를 이해합니다. 브라우저에서 직접 실행하는 실습 코드로 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“현대적인 로그 형식 이해” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)(으)로 돌아가기