Interesting talk. Too much time spent trying to convince, instead of showing examples of why canonical logs are better and how to easily do it and other tools that support them. Hopefully since openTelemetry still hasn't done much in the logging area, they can pull these ideas and make it simple to implement
I second this. Loved the talk and the ideas, and I was convinced halfway through the presentation. I needed to see some implementations or examples. Oh well, it’ll just be one more thing to research.
10:38 logs are just bits of data that haven’t been mapped into your data model. If it’s of ongoing interest, it should probably be persisted in a database with referential links to the relevant database records. Then you can properly query the data and link it to all the relevant information.
Thanks
Thank you very much @juliojordan. This is much appreciated! ⭐️
Canonical logs, such a powerful pattern.
Obs 1.0: we need to slog for structured logs..
Obs 2.0: who let the logs out!!?!
Interesting talk. Too much time spent trying to convince, instead of showing examples of why canonical logs are better and how to easily do it and other tools that support them. Hopefully since openTelemetry still hasn't done much in the logging area, they can pull these ideas and make it simple to implement
I second this. Loved the talk and the ideas, and I was convinced halfway through the presentation. I needed to see some implementations or examples. Oh well, it’ll just be one more thing to research.
10:38 logs are just bits of data that haven’t been mapped into your data model. If it’s of ongoing interest, it should probably be persisted in a database with referential links to the relevant database records. Then you can properly query the data and link it to all the relevant information.
Sorry but Mr Datadog needs another yacht.
Show request.latency in wide structured logs please, and calculate the price as well
goated