1. Heroku, "The Twelve-Factor App," Factor XI. Logs. The canonical source states, "A twelve-factor app never concerns itself with routing or storage of its output stream...each process’s stream will be captured by the execution environment...and routed to one or more final destinations for viewing and long-term archival." This directly supports the concept of the environment capturing and routing logs to a central location. (Source: https://12factor.net/logs)
2. Cisco, "Cloud Native Technologies and Microservices," Cisco Live Presentation BRKCLD-1001 (2019). This presentation discusses the 12-factor app as a foundational set of principles for building cloud-native applications. In the section covering Factor XI (Logs), it emphasizes that applications should log to stdout/stderr and let the platform (execution environment) handle aggregation and forwarding to systems like ELK or Splunk. (Specific slide reference: "12 Factor Apps - XI. Logs").
3. Pahl, C., & Jamshidi, P. (2016). "Microservices: A Systematic Guideline." In 2016 IEEE International Conference on Services Computing (SCC), pp. 438-445. This academic paper reviews microservices principles, referencing the 12-factor app. It notes under the logging pattern that "microservices should not be concerned about the log storage, but should write logs to the standard output. The environment should be responsible for collecting and processing the logs." (Section IV.A. Guideline G1: The Twelve-Factor App). DOI: 10.1109/SCC.2016.65