Spring Boot 4 Microservices & REST APIs · レッスン

ELK Stackによる集中ログ管理

Elasticsearch、Logstash、Kibanaを設定し、ログの一元管理と分析を行います。

「ELK Stackによる集中ログ管理」はCoddyKit上の無料Spring Boot 4 Microservices & REST APIsレッスンです。これはレッスン1/3です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはSpring Boot 4 Microservices & REST APIs学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Spring Boot 4 Microservices & REST APIsコースには全3レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Why Centralized Logging?

In a microservices world, applications don't run as one big piece. Instead, they're many small, independent services.

This means logs are scattered across many servers and containers. Finding issues becomes a huge challenge without a central place to view them all.

Debugging: Hard to trace requests across services.
Monitoring: Difficult to spot trends or errors.
Maintenance: Manually checking logs is time-consuming.

Meet the ELK Stack

The ELK Stack is a popular solution for centralized logging. It's a powerful collection of three open-source tools:

Elasticsearch: Stores and indexes logs.
Logstash: Processes and transforms logs.
Kibana: Visualizes and analyzes logs.

Together, they create a robust pipeline for all your application logs.

Elasticsearch: Data Storage

Elasticsearch is a highly scalable search engine. It's built for speed and can handle vast amounts of data, like all your application logs.

Indexing: Organizes logs for fast searching.
Scalability: Easily handles growing log volumes.
Powerful Search: Allows complex queries to find specific events or patterns.

Think of it as the super-efficient database for your logs.

Logstash: Data Pipeline

Logstash is the data processing engine of the ELK stack. It collects logs from various sources, transforms them, and then sends them to Elasticsearch.

It works like a funnel with three main stages:

Inputs: Where logs are collected from (e.g., files, network, message queues).
Filters: Where logs are parsed, enriched, or modified (e.g., extract data, remove sensitive info).
Outputs: Where processed logs are sent (e.g., Elasticsearch).

Kibana: Visualization & Analysis

Kibana is the user interface that sits on top of Elasticsearch. It lets you explore, visualize, and build dashboards from your log data.

With Kibana, you can:

Search and filter logs in real-time.
Create interactive charts and graphs.
Build custom dashboards to monitor application health.
Identify trends and troubleshoot issues quickly.

Spring Boot Logging Basics

Spring Boot applications use SLF4J as a logging facade and Logback as the default implementation.

By default, Spring Boot logs to the console. These logs include timestamps, log levels (INFO, DEBUG, WARN, ERROR), thread names, and the actual log message.

This console output is a common source for Logstash or other agents to pick up.

Simple Spring Boot Logger

Here's a minimal Spring Boot application that demonstrates basic logging at different levels. Run it and observe the console output.

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class LoggingApp {

    private static final Logger logger = LoggerFactory.getLogger(LoggingApp.class);

    public static void main(String[] args) {
        SpringApplication.run(LoggingApp.class, args);
        logger.info("Spring Boot LoggingApp started!");
        logger.debug("This is a debug message.");
        logger.warn("A warning in the app.");
        logger.error("An error occurred!");
    }
}

Getting Logs to ELK

How do logs from your Spring Boot app reach the ELK stack?

A common approach is to use Filebeat. Filebeat is a lightweight shipper that runs on your application servers. It monitors log files or console output and forwards them to Logstash or Elasticsearch.

This makes sure logs are collected reliably without burdening your application.

The ELK Stack Workflow

Let's summarize the typical flow for centralized logging with ELK:

Your Spring Boot Application generates logs (e.g., to console or a file).
Filebeat collects these logs from the source.
Logstash receives logs from Filebeat, processes them (parses, filters).
Logstash sends processed logs to Elasticsearch for storage and indexing.
Kibana queries Elasticsearch to visualize and analyze the log data.

ELK Component Roles

Each component in the ELK stack has a distinct and crucial role. Understanding these roles is key to effective logging.

Lesson Summary

We've explored the importance of centralized logging for microservices and introduced the ELK (Elasticsearch, Logstash, Kibana) stack.

Elasticsearch: Stores and indexes logs for fast searching.
Logstash: Processes and transforms logs from various sources.
Kibana: Provides powerful visualization and analysis tools.
Filebeat: A common agent for collecting logs from applications.

This powerful combination ensures you can effectively monitor and troubleshoot your distributed applications.

よくある質問

「ELK Stackによる集中ログ管理」レッスンは無料ですか？

はい。「ELK Stackによる集中ログ管理」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Spring Boot 4 Microservices & REST APIsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Spring Boot 4 Microservices & REST APIsコースには全3レッスンが含まれています。

「ELK Stackによる集中ログ管理」で何を学びますか？

Elasticsearch、Logstash、Kibanaを設定し、ログの一元管理と分析を行います。ブラウザで直接実行するハンズオンコードでSpring Boot 4 Microservices & REST APIsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Spring Boot 4 Microservices & REST APIsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSpring Boot 4 Microservices & REST APIsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/3です。

「ELK Stackによる集中ログ管理」レッスンにはどのくらい時間がかかりますか？

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

このSpring Boot 4 Microservices & REST APIsレッスンでコードを書いて実行できますか？

はい。すべてのSpring Boot 4 Microservices & REST APIsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

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

← Spring Boot 4 Microservices & REST APIsに戻る