4 ms·

> So when you're designing an observability system, the whole ball game is about capturing and constraining the cardinality of that metadata. If your world is

> So when you're designing an observability system, the whole ball game is about capturing and constraining the cardinality of that metadata. If your world is only time series databases that struggle with cardinality, then sure. Fortunately, there's a lot more tools out there, some of which do just fine with high cardinality data. I don't really agree much with your entire comment. I think you're looking at observability through the lens of 2010s-era tools, and falling deeply into the trap of thinking that this is the only way to do things.

preseinger 4y ago
My core claim is that telemetry data for a system is always more than the production data for that system. Yes? No? Assuming yes, everything else I'm claiming is noncontroversial.
- phillipcarter 4y ago
  I count about a dozen claims, so I'm not really sure what to begin with. But I disagree with your comment here too.
  - preseinger 4y ago
    (shrug) OK. I'm a domain expert here, but that doesn't mean my claims are infallible, of course. Your call. Good luck.
    - LewisJEllis 4y ago
      most or all of the observability domain experts i'm familiar with either stopped talking about "pillars" several years ago, or have been actively speaking against the "3 pillars" framing for several years most of your takes here sound like they're from somewhere around 2016-2018
- remram 4y ago
  I don't think anyone opposes that, but I don't think that's your "core claim". Your core claim is that this is a huge problem, one that makes OpenTelemetry "a technological dead-end", and that "the whole ball game is about capturing and constraining the cardinality of that metadata". That is what it would be nice to have you justify some more. After all, the same could be said of logs, or internal traffic when using microservices/DBMS (request cardinality/traffic will be multiplied).

preseinger 4y ago

My core claim is that telemetry data for a system is always more than the production data for that system. Yes? No? Assuming yes, everything else I'm claiming is noncontroversial.

phillipcarter 4y ago
I count about a dozen claims, so I'm not really sure what to begin with. But I disagree with your comment here too.
- preseinger 4y ago
  (shrug) OK. I'm a domain expert here, but that doesn't mean my claims are infallible, of course. Your call. Good luck.
  - LewisJEllis 4y ago
    most or all of the observability domain experts i'm familiar with either stopped talking about "pillars" several years ago, or have been actively speaking against the "3 pillars" framing for several years most of your takes here sound like they're from somewhere around 2016-2018
remram 4y ago
I don't think anyone opposes that, but I don't think that's your "core claim". Your core claim is that this is a huge problem, one that makes OpenTelemetry "a technological dead-end", and that "the whole ball game is about capturing and constraining the cardinality of that metadata". That is what it would be nice to have you justify some more. After all, the same could be said of logs, or internal traffic when using microservices/DBMS (request cardinality/traffic will be multiplied).