Abra sua Caixa de Métricas. Agora!

Abilio Esteves, Arquiteto de Aplicações

16/02/2019
 Métricas
O que são, para que servem e como usar

2
Software is Hard!

3
Análise de Séries Temporais

Identifier -> (t0, v0), (t1, v1), (t2, v2)…

4
 Observability
Logs, Traces e Métricas

5
Sistemas em Produção

Sinais nervosos Métricas

Sintomas Alertas

Doença Bug

Cirgurgia Fix

6
Caixas de métricas

7
Cloud

• Clusters de servidores de aplicação

• Crescimento horizontal e vertical dinamizado

• Distribui a responsabilidade de processar

requests

• Reduz significativamente indisponibilidade de

serviço

8
Logs

• Evidencia eventos críticos, importantes e cotidianos no

ciclo de vida de uma aplicação

• Nível de detalhe provoca alto volume de dados

• Adequado para análises de causa raíz

9
Traces

• Metadados da execução de um único request

dentro de uma arquitetura distribuída

• Auxilia análises de causas raíz

10
Métricas

• Valores agregáveis em counters,

gauges, histograms e summaries

• Aplicabilidade de métodos
estatísticos sobre os dados

11
Resumo

Dados agregáveis de um request

Baixo
Volume

Métricas
Dados
Traces agregáveis
Dados de
Requests

Eventos agregáveis
Logs
Alto Eventos por request Eventos
Volume
Eventos agregáveis
de um request

12
 Prometheus 101
Pacotão Básico

13
Intro

14
 https://bit.ly/2GQtfCF
Demo Single Instance
/query_range /metrics

Grafana

Counters Gauges Histograms

15 IBM Confidential
 Prometheus 102

16
 PromQL Cheatsheet
Selectors
• Instant vector selectors:
• In the simplest form, only the metric
name is needed:
http_requests
• One can filter the results by regexping
over the dimensions:
http_requests{status=!”200”}
• Available matching operators:
=, !=, =~, !~
• Range vector selectors:
• Enable the selection of a range of
samples back from the current instant:
http_requests{status=!”200”}[5m]
• s seconds; m minutes; h hours; d days;
w weeks; y years
• [<time>] only applicable after a metric
selector
• Its also possible to offset the current time
of observations:
http_requests{status=!”200”} offset 5m
17
Operators
• Binary:
• + addition, - subtraction, * multiplication, /
division, % modulo, ^ exponentiation
http_requests{status=”500”}/http_requests
• Comparison:
• == equal, != not-equal, > greater-than, < less-
than, >= greater-or-equal, <= less-or-equal
http_requests{status=”500”}/http_requests > 0.2
• Logical/set:
• Only between instant vectors
• and intersection, or union, unless complement
http_requests{status=”500”} or
http_requests{status=“400”}
• Aggregation:
• Only application over a simple instant vector
• sum, min, max, avg, stddev, stdvar, count,
count_values, bottomk, topk, quantile
• Can be aggregated over all dimensions or
preserve distinct dimensions by using without
and by
sum(http_requests) by (status)
Functions
• Operations on range vectors will always
return instant vectors
• increase(v range-vector): calculates how
the counter increased over the range
specified. Use it with Counters only.
increase(http_requests{status=“500”}[1m])
• rate(v range-vector): calculates the
average per second rate of increase over
the range specified. Use it with Counters
only.
rate(http_requests{status=“500”}[1m])
• predict_linear(v range-vector, t scalar):
predicts what the value of the current range
vector can be in t seconds with simple
linear regression. Use it with Gauges only.
predict_linear(http_requests{status=“500”}[9m], 3600)
• deriv(v range-vector): calculates the per-
second derivative of the given range vector,
using simple linear regression. Use it with
Gauges only.
deriv(http_requests{status=“500”}[9m])
Demo Federation

/query_range /federate /metrics

18 https://bit.ly/2GQtfCF
Performance

19 IBM Confidential
Performance

20
Performance

Rede ~ entropia do /metrics

CPU
1. Recording Rule and Alert Evaluation
2. Write ahead logs
3. Block compaction

Memória ~ bloco de 2h mais recente

Disco

& ' () ' )* ' )+

!"#$ = ,-.
/0/2

21
 https://goo.gl/DuUSvr

22