The document discusses various aspects of monitoring, including metrics aggregation, log aggregation, alerting, visualizations, and distributed tracing. It outlines best practices for logging, such as including timestamps and logging all application errors, while cautioning against logging insignificant events and providing personal identifiable information. Additionally, it references tools like OpenTracing and OpenCensus and offers resources for further exploration.

1. Monitoring the right
way
Dan Barker
@barkerd427

2. ● Metrics aggregation
● Log aggregation
● Alerting and visualizations
● Distributed Tracing
Observability Tools
@barkerd427

3. ● Metrics aggregation
● Log aggregation
● Alerting and visualizations
● Distributed Tracing
Observability Tools
@barkerd427

4. ● Easy to get started
● Install an agent
● Built in
Metrics Aggregation
@barkerd427

5. ● Some built in
● Requires dev work
● Security risks
Log Aggregation
@barkerd427

6. ● Requires more
understanding
● Can cause negative
impact
Alerts and Visualizations
@barkerd427

7. ● Not necessary
● Not built in
● Less mature
Distributed Tracing
@barkerd427

8. Push vs Pull?
@barkerd427

9. OpenMetrics
@barkerd427

10. Use Business
Metrics
@barkerd427

11. Log aggregation
tools are for logs!
@barkerd427

12. ● actually have logs
● format in JSON
Do’s of logging
@barkerd427

13. ● include a timestamp
● time should be UTC
Do’s of logging
@barkerd427

14. ● log all application errors
● write messages in a
human-readable form
Do’s of logging
@barkerd427

15. ● log info data in prod
● log insignificant events
● log PII
Don’ts of logging
@barkerd427

16. “A joke that works is
complete knowledge in a
nanosecond.”
– Steve Martin
@barkerd427

17. There are no
“informational”
alerts!
@barkerd427

18. OpenTracing
@barkerd427

19. OpenCensus
@barkerd427

20. ● https://monitoring.danbarker.codes
● https://www.practicalmonitoring.com/
● https://opensource.com
● https://danbarker.codes
Resources
@barkerd427