~/talk

The Prometheus monitoring system

Talkat Incontro DevOps 2017 · on Friday, 2017-03-10· [observability, devops-and-delivery]
links:none on file
slides:none on file

Prometheus is a single Go binary monitoring system and TSDB that proves useful specifics: it replaces New Relic for a Rails stack, adds node exporter and local statsd aggregators, and uncovers 70% of statsd events lost until UDP was fixed. It uses a pull model with push vs pull tradeoffs, a label-based dimensional model, a PromQL for rates and error percentages, recording rules plus alertmanager, float64 storage and no clustering, and a working case of dashboards and per-controller latency and error alerts.

AI-written summary · about

  1. 0:00Start
  2. 3:29What is Prometheus?
  3. 5:39What does Prometheus NOT do?
  4. 10:38Data Model
  5. 11:49Text exposition format
  6. 12:19Non-SQL Query Language
  7. 14:50Pull vs. Push
  8. 20:45Stateful Client Libraries
  9. 22:38Case Study
  10. 24:33Prometheus Instrumentation
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.