After you've written, debugged, profiled, and monitored your Go code, you need to monitor your application in the long term for performance regressions. Adding new features to your code is useless if you can't continue to deliver a level of performance that other systems in your infrastructure depend on.
In this chapter, we will learn about the following topics:
- Utilizing the Go Prometheus exporter
- Application performance monitoring (APM) tools
- Service-level indicators and service-level objectives (SLIs and SLOs)
- Utilizing logging
Understanding these concepts should help drive you to write performant code over the longer term. When working on larger-scale projects, work often doesn't scale well. Having 10 times the number of engineers often does not guarantee 10 times the output. Being able to programmatically quantify code...