* conceptually friendly to ~everybody
* doesn't depend on your code exiting or error ing cleanly
* helps you generate traces from ordinary events (yay)
* lets you do the poor man's debugger thing (ehh.. but rounding up)
* great for grepping
* wasteful: you're spewing a ton of redundant data constantly
* this makes it subject to all the same terrific degradation scenarios as Logs Classic
* the oops-did-i-ddos-myself-agains
* unfriendly to graphical exploration in aggregate
* unfriendly to APM model
I want to be encouraging! and inclusive! This hits most of the points!
- structured data
- raw requests
- read time aggregation
- first-person narrative
🌟🎉🌈
For example, maybe you are looking for a problem which (unbeknownst to you) only turns up under ios10,
Now, stripe is logging out SOME context each time: request ID, user ID etc.
Which, as we've discussed, is the ultimate arbiter of whether or not something is observability. This does not qualify.
....And then a columnar store and exploratory UI. Hrm. I hadn't really thought of it this way, but I guess o11y demands a GUI.
Great for crunching known unknowns. Less great for o11y.
... But I could've found those answers in a minute or two, if I'd had honeycomb. 😔