What if Mesos Metrics Collection was a Snap?
summary
Shows a working Snap collector that polls Mesos master and agent APIs every ~10 seconds, respects leader redirect handling, and exposes hundreds of metrics with dynamic namespaces per framework and executor so you can attribute CPU and memory to Marathon versus Chronos. Snap decouples collection, processing and publishing, supports live plugin upgrades and a snap tribe gossip rollout for thousands of nodes. Open source Mesos plugin is on GitHub with a Vagrant demo using InfluxDB and Grafana; demo hiccuped but the repo provisions everything.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:27What is Day 2 Operations
- 2:33Mesos Metrics API
- 2:57Redirect
- 4:36Endpoints
- 7:12Snap Overview
- 11:37Snap Collector Plugin
- 11:54Mesos Metrics Collection
- 12:59Mesos Namespaces
- 14:01Snap Demo
- 15:15Metrics Graph
- 16:26Demo
- 16:37More information
related talks
06mMy cloud makes pretty pictures
30mDay 2 Operations Best Practices with Apache Mesos
30mCheap DIY Monitoring with OSS Analytics & Visualization
18mJon Schneider at SpringOne Platform 2017
16mMicroMon: A Monitoring Framework for Tackling Distributed Heterogeneity
42mMonitoring Mesos with InfluxDB & the TICK Stack
08mStreamlining continuous profiling with snaps and charms!
59mDistributed Tracing and Monitoring with OpenCensus