Framingham Go Meetup - October 2016
•Download as PPTX, PDF•
0 likes•312 views
As part of the team delivering Snap, an open telemetry framework, I've run through dozens of use cases where gathering disparate metrics from services can roll up into meaningful diagrams for operations engineers and developers alike. I will introduce you to the concept of telemetry by talking through the basics then using Snap's plugin model to collect, process and publish these measurements into meaningful graphs using open source tools.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (11)
Similar to Framingham Go Meetup - October 2016
Similar to Framingham Go Meetup - October 2016 (20)
More from Matthew Broberg
More from Matthew Broberg (9)
Recently uploaded
Recently uploaded (20)
Framingham Go Meetup - October 2016
- 1. Go Telemetry Frameworks A view of what’s out there Matt Brender (@mjbrender)
- 2. Hey 👋 2 • Community Builder • Podcaster • More Ops than Dev • Monitoring Centric • Aspiring Gopher • Still like Ruby
- 3. What Is Telemetry? 1.What you can measure ......... 2.The process of persisting it • Telemetry - the process of using equipment to take measurements of something and send them to another place • Metrics - measurements of facts throughout the data center • Analytics - the method of logical analysis that determines the consequences of information
- 5. Visibility at all layers 5 ? App OS HW Analytics Pipeline Dashboards
- 6. What Is Telemetry? What How Application Availability ping Operating System Performance psutil Hardware Utilization Intel Performance Counter Metrics (PCM)
- 7. What Is Telemetry? What How Why Application Availability ping SLA compliance Operating System Performance psutil System performance Hardware Utilization Intel Performance Counter Metrics (PCM) Scaling capacity
- 9. 9 Telemetry
- 10. InfluxDB OpenTSDB KairosDB Graphite Prometheus ElasticSearch Bosun 10 Snap collectd StatsD telegraf beats Logstash diamond Grafana Sensu Ganglia RRDtool Nagios Facette Vector (Netflix) Blue = in Go && Telemetry Yellow = Go & Monitoring, but not strictly Telemetry
- 11. What Is Telemetry? (revisited) What Query Collect Process Publish Visualize Application Availability ping ? ? ? ? Operating System Performance psutil ? ? ? ? Hardware Utilization PCM ? ? ? ? How Expanded
- 12. What Is Telemetry? (revisited) What Query Collect Process Publish Visualize Application Availability ping ? ? ? ? Operating System Performance psutil ? ? ? ? Hardware Utilization PCM ? ? ? ? How Expanded Snap Grafana
- 13. 13
- 14. Jump right in • Update an existing Snap Plugin • Write your own plugin • Help with the Snap framework • Backend (under /pkg) 14 • Build apps with /healthz endpoints • Learn about Heapster and cAdvisor or you can:
- 15. 15 Start using Snap! • snap-telemetry.io • github.com/intelsdi-x Find me: • on The Geek Whisperers • and @mjbrender
Editor's Notes
- Ground rules for today – we’re in this together. Ask questions. Let’s all trust but verify.
- Read for intro to hugops: https://www.pagerduty.com/blog/hugops-in-practice/
- Telemetry is the stuff you can measure and the process of capturing it: from the heat generated on a CPU core to the throughput of Nginx* running in a Docker* container on a Kubernetes cluster. It’s all measurable and it’s all summarized in that one word.
- Wouldn’t it be nice if it was something more like this. A workflow that starts with collection, regardless of the layer. Gather all the raw metrics of potential value we can find in our environment that may lead to informed decisions downstream. Then we add a great deal of value with the right amount of processing of that information. Perform some basic filtering or decorate our information by adding further context. This processed information is then published to one or more platforms. Our workflow should be able to treat all endpoints as the same, since they’re guaranteed to change with time. This information would then be pulled into real use cases for the different parts of the business: better monitoring, orchestration and scheduling, billing/chargeback. This data is valuable in many ways to many people who can all have their own view of it. What was once chaos is now actually our advantage. We are going to harness this chaos to make hugely intelligent systems out of what used to call white noise. TRANSITION: What might you want to specifically achieve in each of these phases?
- For spooling https://github.com/graphite-ng/carbon-relay-ng Great examples: http://oss.oetiker.ch/rrdtool/gallery/index.en.html
- Justification for why you need this? Can’t fix what you can’t see Can’t improve what you didn’t measure
- Our roadmap is designed by the developers involved in the project. To see how the framework continues to evolve, review the open RFCs (requests for comment) on GitHub. We keep a wish list of desired plugins as well. TRANSITION - One specific feature request involves distributed workflow Source -