I’ve been evolving an observability ranking for the APIs I track for a couple years now. I’ve been using the phrase to describe my API profiling and measurement approach since I first learned about the concept from Stripe. There are many perspectives floating around the space about what observability means in the context of technology, however, mine is focused completely on APIs, and is more about communicating with external stakeholders, more than it is just about the monitoring of systems. To recap, the Wikipedia definition for observability is:
Formally, a system is said to be observable if, for any possible sequence of state and control vectors, the current state can be determined in finite time using only the outputs (this definition is slanted towards the state space representation). Less formally, this means that from the system’s outputs it is possible to determine the behavior of the entire system. If a system is not observable, this means the current values of some of its states cannot be determined through output sensors. https://goo.gl/DcdMCz #DataIntegration #ML
