So basically, if I understand correctly, Booking com is still getting logs, traces and metrics. Just that they are using events as the origin of this data. This allows like one entry point on the machine-level for all three types of data.
As someone who had their fair share of setting up different logging, tracing, and monitoring on projects, I can see the advantage of keeping a single unit of work as a single entry that you can examine further if needed. What would be the drawback of this? Are there generally available solutions like the one booking implemented?
Great article, Fernando, and thanks for the mention!
Interesting article Fernando.
So basically, if I understand correctly, Booking com is still getting logs, traces and metrics. Just that they are using events as the origin of this data. This allows like one entry point on the machine-level for all three types of data.
Also, thanks for the mention!
Great summary, Saurabh.
One critical piece of observability is the use of structured information.
There is something magical in the ability to query what happens in your systems.
I loved the article; thanks for the mention, Fernando!
Great article 👏👏
As someone who had their fair share of setting up different logging, tracing, and monitoring on projects, I can see the advantage of keeping a single unit of work as a single entry that you can examine further if needed. What would be the drawback of this? Are there generally available solutions like the one booking implemented?
Great article, Fernando, and thanks for the mention!
Thanks, Akos. Honestly, I'm not aware of a similar open source solution.
Thanks Fernando, me neither 🫣