0Pricing
System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) · Aula

Tipos de métricas explicados

Compreenda os tipos fundamentais de métricas: indicadores, contadores, histogramas e resumos. Aprenda quando e como aplicar cada tipo para um monitoramento eficaz.

Tipos de métricas explicados é uma aula grátis de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

What are Metric Types?

Welcome to "Types of Metrics Explained"! In observability, metrics are crucial for understanding your system's health and performance.

But not all numbers are the same! Categorizing metrics helps us collect, store, and analyze them effectively.

We'll explore the four fundamental types: Gauges, Counters, Histograms, and Summaries.

Gauges: Snapshot of Now

A Gauge represents a single numerical value that can go up and down over time. Think of it like a car's speedometer or a thermometer.

Gauges are perfect for capturing the current state of a system at a specific moment.

  • Use for: Current CPU usage, memory consumption, queue size, temperature.
  • Nature: Point-in-time value.

Gauge Code Example

Here's a simple Java example simulating a gauge tracking current CPU utilization. Notice how its value can change freely.

public class Main {
  public static void main(String[] args) {
    double cpuUsage = 0.5; // 50% CPU
    System.out.println("Current CPU Usage: " + cpuUsage);

    // Later, CPU usage might change
    cpuUsage = 0.8; // 80% CPU
    System.out.println("Updated CPU Usage: " + cpuUsage);

    cpuUsage = 0.3; // 30% CPU
    System.out.println("Further Updated CPU Usage: " + cpuUsage);
  }
}

Counters: Always Increasing

A Counter is a cumulative metric that only ever increases. It represents a total count of something that has occurred since the system started.

It can reset to zero only when the monitored system restarts.

  • Use for: Total requests served, errors encountered, bytes sent, login attempts.
  • Nature: Monotonically increasing total.

Counter Code Example

This Java example demonstrates a counter for total requests. Each 'request' simply increments the counter.

public class Main {
  private static long totalRequests = 0;

  public static void handleRequest() {
    totalRequests++;
    System.out.println("Requests handled: " + totalRequests);
  }

  public static void main(String[] args) {
    System.out.println("Initial requests: " + totalRequests);
    handleRequest(); // First request
    handleRequest(); // Second request
    // ... more requests later
    handleRequest(); // Third request
  }
}

Histograms: Value Distributions

Histograms sample observations (like request durations or response sizes) and count them in configurable buckets.

They give you insight into the distribution of values, not just the average. This is vital for understanding latency and performance.

  • Benefit: You can calculate percentiles (e.g., 99th percentile latency) on the server side.
  • Use for: Request latency, response sizes, data transfer rates.

Summaries: Pre-calculated Percentiles

Summaries are similar to histograms but often pre-calculate configurable quantiles (like p99, p95, p50) on the client side.

Instead of sending raw data, the client library sends pre-computed statistics (sum, count, and quantiles) to the monitoring system.

  • Benefit: Less data sent over the network, but less flexible for custom percentile calculations later.
  • Use for: Latency measurements where specific percentiles are known to be needed.

Histograms vs. Summaries

Both Histograms and Summaries track distributions, but they differ in where calculations happen:

  • Histograms: Send raw data (counts in buckets). Percentiles are calculated on the server. More flexible for ad-hoc analysis.
  • Summaries: Calculate percentiles on the client and send pre-computed results. More resource-efficient if you know exactly which percentiles you need.

For most modern systems, Histograms are generally preferred due to their flexibility.

Picking the Best Metric Type

Choosing the right metric type is key for effective monitoring:

  • Gauges: For current values that can go up/down (e.g., disk usage, active users).
  • Counters: For cumulative totals that only increase (e.g., total errors, processed items).
  • Histograms: For distributions of values where you need server-side percentile calculation and flexibility (e.g., request durations).
  • Summaries: For distributions where client-side pre-calculated percentiles are sufficient and network efficiency is critical (less common than histograms now).

Metric Type Challenge

Your application processes user orders. You want to track the total number of orders placed since the application started, and also the current number of items in the processing queue.

Key Takeaways on Metrics

Great job! You've now learned about the four fundamental metric types:

  • Gauges: For current, fluctuating values.
  • Counters: For cumulative, ever-increasing totals.
  • Histograms: For understanding the distribution of values and calculating percentiles server-side.
  • Summaries: For pre-calculated percentiles client-side.

Understanding these types helps you choose the right tool for the right job, leading to more insightful monitoring and faster debugging!

Perguntas Frequentes

A aula “Tipos de métricas explicados” é grátis?

Sim — o texto completo de “Tipos de métricas explicados” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry), atualize para CoddyKit PRO. O curso de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) inclui 4 aulas no total.

O que vou aprender em “Tipos de métricas explicados”?

Compreenda os tipos fundamentais de métricas: indicadores, contadores, histogramas e resumos. Aprenda quando e como aplicar cada tipo para um monitoramento eficaz. Você pratica System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)?

Nenhuma experiência prévia é necessária. System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Tipos de métricas explicados”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)?

Sim. Cada aula de System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Tipos de métricas explicados
  2. Estratégias de coleta de métricas
  3. Visualização e alertas de métricas
  4. Cardinalidade de métricas e boas práticas de rotulagem
← Voltar para System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)