"Logs are a stream, and it behoves[sic] everyone to treat them as such. Your programs should log to stdout and/or stderr and omit any attempt to handle log paths, log rotation, or sending logs over the syslog protocol."
If you were being pedantic one might say that logs are a repository for temporally tagged event notifications that have occurred in the past. You can store these temporally tagged event streams in files, in a memory cache, in an email inbox, or a round robin database (RRD).
Not particularly profound, but useful. Logs from disparate processes which share a common time basis however are the systems analyst's go to tool for trying to untangle secondary and tertiary properties of a loosely coupled system.
If you were being pedantic one might say that logs are a repository for temporally tagged event notifications that have occurred in the past. You can store these temporally tagged event streams in files, in a memory cache, in an email inbox, or a round robin database (RRD).
Not particularly profound, but useful. Logs from disparate processes which share a common time basis however are the systems analyst's go to tool for trying to untangle secondary and tertiary properties of a loosely coupled system.