The Mechanics of Metrics
summary
Metrics are time‑series key/value pairs; the talk shows concrete pitfalls and fixes by instrumenting a Monster Combat app with Micrometer and Prometheus, then shipping a micrometer extension that merges into Quarkus core. Counters roll over and cause spikes unless converted with the rate() function; tag permutations create a cardinality explosion if uncontrolled. Precomputed client quantiles are unrecombinable across instances, so use histogram buckets or server-side aggregation. The extension and examples prove the approach works in real Quarkus deployments.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:50Application Metrics
- 2:32Time Series
- 3:20Tags
- 5:50Counters
- 11:02Hits and misses
- 12:02Distribution summaries
- 13:32Count and sum
- 21:05Delaying aggregation
- 25:14Observability
- 29:56Outro
related talks
36mMetrics - What's your code actually doing?
45mMicroProfile Metrics: Practical Use Cases
41mRuby Monitoring State of the Union
44mWelcome to the Metrics
27mGrand Treatise of Modern Instrumentation and Orchestration
23mYou Get What You Measure—Why Metrics Are Important
18mJon Schneider at SpringOne Platform 2017
50mHow to Get Started with Metrics?
