A diversion into logging. Log files are good to have, but they tend to lie. For example, it’s very common for the logging of a few error classes to take up a large proportion of a space in a log file but, in actuality, occur in a very low proportion of requests.
Because logging successes is redundant in most cases (and would blow out the disk in most cases) and because engineers often guess wrong on which kinds of error classes are useful to see, log files get filled up with all sorts of odd bits and bobs. Prefer logging as if someone who has not seen the code will be reading the logs.
Log aggregation using Elasticsearch, Logstash, and Kibana (ELK)
https://engineering.linkedin.com/blog/2016/10/reducing-the-mttd-and-mttr-of-linkedins-private-cloud
A Primer on Distributed Systems Observability
https://itnext.io/a-primer-on-distributed-systems-observability-a0c2a8e2146c?gi=456159a26eaa