メトリクス収集の戦略
プッシュ型とプル型のモデルを含む、メトリクス収集のさまざまな方法を学びます。メトリクスの抽出に使われる代表的なエージェントやライブラリについても確認します。
「メトリクス収集の戦略」はCoddyKit上の無料System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)コースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Welcome to Metric Collection!
In this lesson, we'll explore how to gather those valuable metrics we discussed previously. Think of it as setting up the 'ears' and 'eyes' for your system!
Collecting metrics is crucial for understanding how your applications and infrastructure are performing. It helps you quickly spot issues and ensure everything is running smoothly.
Two Main Approaches: Push or Pull
When it comes to getting metrics from your systems, there are two fundamental strategies:
- Push Model: The application or a dedicated agent sends metrics to a central collector.
- Pull Model: A central collector fetches metrics from the applications or agents.
Each approach has its own strengths and weaknesses, which we'll explore next.
Understanding the Push Model
In the push model, your application or a local agent actively sends its metrics data to a central metrics store or collector. It's like your app shouting its status updates!
- Pros: Often easier with firewalls (outbound connections only), good for ephemeral (short-lived) jobs that might disappear before a collector can pull, can handle network partitions by buffering data.
- Cons: The collector needs to handle potentially unpredictable incoming load, harder to discover new targets automatically.
Push Model Example (Conceptual)
Here's a simple Java program that conceptually demonstrates pushing a metric. In a real scenario, this would involve sending data over HTTP to a metric collector endpoint.
Try running it to see the idea!
public class MetricPusher {
public static void main(String[] args) {
double cpuUsage = 65.2;
String metricName = "cpu_usage_percent";
// Simulate sending the metric to a collector
System.out.println("Pushing metric: " + metricName + " = " + cpuUsage);
System.out.println(" (Imagine this is an HTTP POST to a collector)");
}
}Understanding the Pull Model
With the pull model, a central metrics collector actively requests or 'scrapes' metrics from your applications or agents at regular intervals. It's like the collector asking, 'Hey, what's your status?'
- Pros: Easier service discovery (collector finds targets), collector controls scrape frequency and load, simpler target configuration.
- Cons: Requires inbound network access to targets, targets need to be long-lived to be scraped, more complex for highly dynamic environments.
Pull Model Example (Conceptual)
This Java example simulates an application exposing a metrics endpoint, ready for a collector to pull from. A real application would run a tiny web server.
Run it to see how an app might make data available.
public class MetricExposer {
public static void main(String[] args) {
String appStatus = "healthy";
int activeUsers = 150;
// Simulate an application making metrics available at an endpoint
System.out.println("Application running...");
System.out.println("Metrics ready for scraping at /metrics endpoint.");
System.out.println(" (Imagine a collector fetches: app_status='" + appStatus + "', active_users=" + activeUsers + ")");
}
}Dedicated Collection Agents
Many systems use dedicated collection agents. These are small programs that run on your server or container, gathering system-level metrics or acting as a proxy for application metrics.
- Prometheus Node Exporter: A popular agent that exposes hardware and OS metrics (CPU, memory, disk I/O) in a format Prometheus (a pull-based system) can scrape.
- Telegraf: A plugin-driven agent that can collect metrics from various sources (databases, message queues, system stats) and output them to different destinations (push or pull).
In-Application Libraries
For application-specific metrics, you often integrate client libraries directly into your code. These libraries allow you to instrument your application to expose custom metrics.
- Micrometer (Java): A vendor-neutral application metrics facade. You instrument your code once with Micrometer, and it can then export metrics to various monitoring systems (e.g., Prometheus, Datadog, Graphite).
- Prometheus Client Libraries: Language-specific libraries (e.g., Java, Python, Go) that let you define and expose metrics directly from your application in Prometheus's scrape format.
Choosing Your Collection Strategy
Deciding between push and pull, or using agents vs. libraries, depends on your specific environment:
- Environment: Cloud-native, on-prem, serverless functions.
- Network Topology: Firewall rules, service mesh.
- Data Volume & Velocity: How much data, how often?
- Existing Tools: What monitoring systems are you already using?
Often, a hybrid approach is used, combining agents for system metrics and libraries for application metrics.
Quick Check on Metrics
You've learned about the two main metric collection models. Let's see if you can distinguish between them.
Recap: Getting Metrics into Action
Great job! You've now grasped the core strategies for collecting metrics.
- We explored the push model, where applications send metrics.
- We also covered the pull model, where a central collector fetches metrics.
- You learned about dedicated collection agents (like Node Exporter, Telegraf) and in-application libraries (like Micrometer, Prometheus client libs) that implement these strategies.
Understanding these collection methods is key to building a robust observability setup!
AI チューターと学ぶ System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) — 無料
ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。
- コース
- 12
- レッスン
- 48
よくある質問
「メトリクス収集の戦略」レッスンは無料ですか？
はい。「メトリクス収集の戦略」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)コースには全4レッスンが含まれています。
「メトリクス収集の戦略」で何を学びますか？
プッシュ型とプル型のモデルを含む、メトリクス収集のさまざまな方法を学びます。メトリクスの抽出に使われる代表的なエージェントやライブラリについても確認します。 ブラウザで直接実行するハンズオンコードでSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)を演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)を始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)は初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/4です。
「メトリクス収集の戦略」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンでコードを書いて実行できますか？
はい。すべてのSystem Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)レッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。