3 ms·
The Docker logging model of line-by-line stdout/stderr doesn't seem very useful beyond debugging in the local console. I prefer configuring the application logg
by tveita 10y ago
The Docker logging model of line-by-line stdout/stderr doesn't seem very useful beyond debugging in the local console. I prefer configuring the application logger to ship logs directly to a proper log system when possible.
E.g. Logback is perfectly happy shipping structured logs directly to Kafka or Elasticsearch, with no need to re-parse the formatted log output.
- deleted 10y ago[deleted]
- sagichmal 10y agostdout/stderr is actually a perfectly lovely default contract between application and operational environment. It's available to all programs, it's sync by default, and the semantics are intuitive.
- jacques_chester 10y ago> The Docker logging model of line-by-line stdout/stderr doesn't seem very useful beyond debugging in the local console. It's a well-understood pattern that Heroku made more visible under "The 12 Factor App". stdout/stderr require no configuration in any language that I'm aware of. Why should the app care about how to wire up logging? That's a platform concern. On Cloud Foundry you get Loggregator, which frankly needs improvement, but for the most part you don't care about how to wire up logging. You print to stdout or stderr and the platform wicks that away to a firehose service for you. You can hook up kafka to spout, or elasticsearch, or anything else you like. Disclosure: I work at Pivotal, we donate the majority of engineering to Cloud Foundry.