Telemetry - what and why
•
0 likes•70 views
Telemetry is the process of collecting data about objects from a distance electronically. It enables answering questions about feature usage, request processing, CPU and memory load, and queue lengths. While logging provides diagnostic information, telemetry provides raw aggregated data that is easy to process and the foundation for alerting and trend analysis. There are different ways to collect telemetry data including pushing from applications or pulling to external storage, and it is typically aggregated using common metrics like counters, gauges, histograms and timers. Telemetry data is required for alerting systems and trend analysis to monitor application and business performance over time.
Recommended
More Related Content
Similar to Telemetry - what and why
Similar to Telemetry - what and why (20)
Recently uploaded
Recently uploaded (20)
Telemetry - what and why
- 1. TELEMETRY
- 2. KIM CHRISTENSEN Senior Developer, Scrum master and Cloud TechLead at SimCorp 2
- 4. “ The science or process of collecting information about objects that are far away and sending the information somewhere electronically -Cambridge Dictionary 4
- 5. TELEMETRY Enables you to answer questions like ◦ What features are used? ◦ How many requests are processed? ◦ What is the CPU and memory load? ◦ What is the queue length? 5
- 6. 6
- 7. LOGGING IS NOT TELEMETRY 7 But they can be correlated
- 8. LOGGING IS NOT TELEMETRY Logging is ◦ Diagnose errors and code flows ◦ Used for in-depth investigations Telemetry is ◦ Raw data ◦ Easy to process ◦ Foundation for alerting 8
- 9. WHY NOT LOGGING AS TELEMETRY? ◦ Logs use much more space ▫ Prometheus: Average 1.37 bytes ▫ InfluxDB: Average 3 bytes ◦ Post-processing is necessary 9
- 11. WHY? ◦ Application performance ▫ Which parts are slow? ▫ Memory leaks ▫ Monitor external dependencies ◦ Business performance ▫ How does new features affect customers? ▫ Which parts of the system is used? ◦ Visibility ▫ Base decisions on facts ▫ Create reports on data 11
- 12. SAMPLE 12
- 13. SAMPLE 13
- 14. SAMPLE 14
- 15. HOW TO COLLECT TELEMETRY?3 15
- 16. TYPES OF TELEMETRY White-box ● How many times an action has been performance ● Processing speed Gray-box ● Dynamic instrumentation of code ● HTTP server metrics Black-box ● CPU load ● Memory load 16
- 17. WAYS TO COLLECT DATA Pull Push 17
- 18. WAYS TO COLLECT DATA - PUSH ◦ Pros ▫ Allows for real-time data ▫ Data can be sent before shutting down ▫ No external access to app is needed ◦ Cons ▫ All apps needs to know location of storage ▫ Storage cannot easily be moved 18
- 19. WAYS TO COLLECT DATA - PULL ◦ Pros ▫ Apps don’t know the location of the storage ▫ Storage can easily be moved ◦ Cons ▫ Cannot provide real-time data ▫ Data can be lost when shutting down ▫ External access to app is needed 19
- 20. AGGREGATION TYPES Common aggregation types: ◦ Counter ▫ Incremental values ◦ Gauge ▫ Current value ◦ Histogram ▫ Group values in buckets ◦ Timer ▫ Measure time, usually a combination of the types above 20
- 21. WHY AGGREGATE? ◦ Pros ▫ Less memory needed ▫ Uses less bandwidth ▫ Often raw values aren’t need ◦ Cons ▫ Requires more computing ▫ Precision loss 21
- 22. WHAT TELEMETRY NOT IS4 22
- 23. WHAT TELEMETRY NOT IS ◦ Profiling ▫ Profiling is used during development ◦ Debugging ▫ Debugging is done during development ▫ In extreme cases in production ◦ Logging ▫ Provides textual context ▫ Can be correlated with telemetry data 23
- 25. TELEMETRY IS REQUIRED FOR ALERTING AND TRENDING 25
- 26. ALERTING Telemetry is the foundation of alerting ◦ What alerts to you need? ◦ When should the alert be raised? ◦ Is it a spike? Data resolution needs to be fairly high 26
- 27. TRENDING ◦ Has the performance degraded since last version? ◦ Has users changed behaviour? Data resolution doesn’t need to be high 27
- 28. WHAT TO COLLECT? Could be ◦ Version ◦ Machine ID ◦ User ID ◦ Memory and CPU consumption ◦ Customer ID ◦ Request path ◦ Latency 28
- 29. WHAT TOOLS TO USE? A lot of tools exists ◦ Prometheus (OSS) ◦ TICK stack (InfluxData, OSS) ◦ Okanshi (OSS) ◦ AppMetrics (OSS) ◦ AppDynamics ◦ Graphite (OSS) ◦ Grafana (OSS) ◦ and more... 29
- 31. Thanks! ANY QUESTIONS? You can find me at @Xharze kimworking@gmail.com 31