| • Logging as a ubiquitous practice in software development
|
| • Debate on whether to remove logging statements after initial debugging phase or keep them for future reference
|
| • Importance of context in log messages, including machine information, user IDs, and trace IDs
|
| • Benefits of standardizing log format for easier analysis and correlation across systems
|
| • Trade-off between verbosity and relevance in logging, with some arguing that excessive detail is unnecessary
|
| • The importance of structured logging for machine readability
|
| • Comparison between JSON and logfmt (a key-value pair format) for logging
|
| • Discussion on the trade-off between human readability and machine parsability
|
| • Recommendation to keep a flat structure in logs, especially with JSON
|
| • Consideration of what belongs in logs versus what belongs in a database
|
| • Definition of structured logging as opposed to event logs or access logs
|
| • Advice against storing primary application logs in the same system that needs to run them (e.g. not storing logs in the database)
|
| • Consistency of log output with key-value pairs in logfmt format
|
| • Contextual information in logs for easier pattern recognition
|
| • Use of context to carry contextual information such as user ID and hostname
|
| • Challenges with using context deadline exceeded errors in distributed systems
|
| • Difficulty in distinguishing between different types of context cancellation
|
| • Potential improvements to Go's error handling, including adding a string parameter to the cancel function
|
| • Error messages should be unique within an app
|
| • Logs can be used for error handling and troubleshooting
|
| • Including context in logs can help with debugging complex systems
|
| • Writing log entries for the audience, not just for oneself
|
| • Centralizing error strings for easier maintenance and internationalization
|
| • Log levels (debug, info, warning, error, critical) and their use cases
|
| • Use of separate packages for developer vs production logging
|
| • Benefits of having runtime log-level changing capabilities
|
| • Importance of a standardized interface for logging in Go
|
| • Trade-offs between log verbosity, allocation rate, and performance impact on applications
|
| • Mat Ryer quizzes Jon Calhoun on Java's println methods
|
| • Discussion of logging vs metrics and the trade-offs between them
|
| • Ed Welch explains Loki as a time-series database for strings
|
| • Benefits and drawbacks of combining logs and metrics in one system
|
| • Importance of specialized tooling (logs, metrics, traces) for big distributed systems
|
| • Use cases for including assertions about logged messages in testing
|
| • Logging vs metrics: different approaches to software development and what to prioritize
|
| • Importance of event timestamp accuracy in logs versus metrics
|
| • Challenges of dealing with large amounts of log data (petabytes)
|
| • Loki's approach to indexing metadata instead of full text, and its optimization for parallelism and object stores
|
| • Unpopular opinions segment: Ed Welch mentions he doesn't have an unpopular opinion but laughs about the goal of having one
|
| • Integration testing being a net loss
|
| • Ed Welch's unpopular opinion on not doing integration testing
|
| • Difficulty with large-scale integration tests, including false positives and maintenance issues
|
| • Value in having integration tests available for local development, but not as a hard requirement
|
| • Running integration tests against operational data or clusters
|
| • Keeping integration test scope small and purposeful, running them on-demand
|
| • Ed Welch's opinion that Windows is the best desktop OS
|
| • Comparison of Windows to macOS and Linux
|
| • Keyboard shortcuts and copy-paste functionality differences between Mac and Windows
|
| • Challenges of switching from one operating system to another
|
| • Terminal commands and interrupt behavior on Windows and Mac
|
| • Clipboard management and history tools
|
| • Editing and post-production process for podcasts |
