0Pricing
System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) · レッスン

最新のログ形式を理解する

構造化ロギングとJSONなどの一般的な形式について学びます。構造化ログがプレーンテキストよりも機械的な解析や分析に適している理由を理解します。

「最新のログ形式を理解する」はCoddyKit上の無料System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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時間対応のAIチューター）、System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)コースには全4レッスンが含まれています。

「最新のログ形式を理解する」で何を学びますか？

構造化ロギングとJSONなどの一般的な形式について学びます。構造化ログがプレーンテキストよりも機械的な解析や分析に適している理由を理解します。 ブラウザで直接実行するハンズオンコードでSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)を演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)を始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)は初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン1/4です。

「最新のログ形式を理解する」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンでコードを書いて実行できますか？

はい。すべてのSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. 最新のログ形式を理解する
  2. 集中ログ管理の概念
  3. ログ収集とパースの基礎
  4. 構造化ロギングとログレベル
← System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)に戻る