Tracing: Structured Logging, but better in every way

Re:Tracing: Structured Logging, but better in every way by jauntywundrkind on Wednesday September 20, 2023 @11:13AM (#37585244)

What's most incredible to me is how close tracing feels in spirit to me to event-sourcing.

Here's this log of every frame of compute going on, plus data or metadata about the frame.... but afaik we have yet to start using the same stream of computation for business processes as we do for it's excellent observability.

[ Parent | on HN ]

Re:Tracing: Structured Logging, but better in every way by alexisread on Wednesday September 20, 2023 @01:25PM (#37586991)

Any of the Clickhouse-based Otel stores can do event sourcing - just set up materialised views on the trace tables. I know the following use CH: https://uptrace.dev/ https://signoz.io/ https://github.com/hyperdxio/hyperdx

[ Parent | on HN ]

Re:Tracing: Structured Logging, but better in every way by juliogreff on Wednesday September 20, 2023 @02:50PM (#37588335)

As a matter of fact, at a previous job we used traces as a data source for event sourcing. One use case: we tracked usage of certain features in API calls in traces, and some batch job ran at whatever frequency aggregated which users were using which features. While it was far from real time because of the sheer amount of data, it was so simple to implement that we had dozens of use cases implemented like that.

[ Parent | on HN ]