putting a bunch of engineers on a team calling them an "observability engineering team" does not, regrettably, mean you are getting any observability out of them or their work.
(no hate to the wonderful engineers on those teams, i know you didn't get to choose your title)
(no hate to the wonderful engineers on those teams, i know you didn't get to choose your title)
some ways to spot the difference:
⛔️ prometheus
⛔️ "how to avoid high cardinality problems"
⛔️ log aggregators
⛔️ unstructured data
⛔️ metrics, anything smells like statsd
✅ events, spans
✅ traces (fully integrated)
(or read the whole thing honeycomb.io/blog/so-you-wa…)
⛔️ prometheus
⛔️ "how to avoid high cardinality problems"
⛔️ log aggregators
⛔️ unstructured data
⛔️ metrics, anything smells like statsd
✅ events, spans
✅ traces (fully integrated)
(or read the whole thing honeycomb.io/blog/so-you-wa…)
this handy cheat sheet brought to you by yet another sad engineer who wants nice things but can't have them because "we already do that! we have a whole team!"
in other words: (new sticker) 
