From tracking revenue to knowing about data quality issues, vendor and data products don't sell on simply providing information. Value comes from action.
Interesting point about observability being disconnected from action. I guess the issue resolution process/system should be put in place at the same time as implementing the test suite, otherwise you're only solving half the problem. Software development solves this with clear tests at merge time, but since data pipelines can fail at any time based on the data itself, it's a trickier problem.
Right. So I totally understand the importance of the tools, I just feel like the term itself (used in marketing, etc) stresses the importance of observability itself, when really it's about how the observations influence your actions.
Interesting point about observability being disconnected from action. I guess the issue resolution process/system should be put in place at the same time as implementing the test suite, otherwise you're only solving half the problem. Software development solves this with clear tests at merge time, but since data pipelines can fail at any time based on the data itself, it's a trickier problem.
Right. So I totally understand the importance of the tools, I just feel like the term itself (used in marketing, etc) stresses the importance of observability itself, when really it's about how the observations influence your actions.