4 ms·
I agree with the sentiment but logging is incredibly simple to implement and is almost completely vendor agnostic (it's up to the log aggregator to make sense o
by nijave 2y ago
I agree with the sentiment but logging is incredibly simple to implement and is almost completely vendor agnostic (it's up to the log aggregator to make sense of the log file, not the software to output data in a specific format).
In addition, there's so much software that logs out of the box with limited support for metrics and traces it's not practical to ignore it.
In general though, I agree it's good to avoid if practical. Tracing is much more helpful in most cases especially when helpful context data is attached to traces.
- linkdd 2y ago> not the software to output data in a specific format I like to output structured log anyway. Not JSON as it's not really human readable but at least in "logfmt" format[1] as it's both human readable and easy to parse. FYI, Go provides `log/slog` which offers structured logging in both formats (JSON and logfmt). [1] - https://brandur.org/logfmt https://brandur.org/logfmt
- nijave 2y agoI more-so meant there's not a single, standard way. Lots of software uses logging libraries with arbitrary serialization formats but you generally need to take each schema into account (one software might use "error" while another uses "err") Compared to OpenTelemetry traces (which many vendors support) that has standardized field names with the ability to attach arbitrary data