Observability vs Monitoring

Observability vs Monitoring

Observability is making sure the product is managed with a better integration of results with the behavior of the system such that there is 99.99% uptime. Monitoring involves constant overseeing of events involving multiple workflows that may slow down a process creating overheads in the holistic process of management. Observability can impact the understanding of results such that they may not be fully complete due to issues in detection of events. Customer happiness and customer satisfaction is dependent on the visibility of the system. Through monitoring the human workflows are monitored which as well supersedes a process where a quality inspection for these workflows is assigned such that monitoring of some human workflows are eliminated. Through observability we will be able to automate some human workflows through a qualitative process of data analytics and automation to achieve a matured system of evaluating the processes.

Through data visualization, logging, tracing, and data analytics, one can achieve the constant overseeing of events. Such processes are testable which gives the client to evaluate a job in better ways than existing methods.

APIs are necessary in such processes that support observability. Such APIs will be delivered as services which allow the customer to load balance them.

4 concerns that the author in (BICALHO, 2019) addresses are: (1) Synthetic checks, (2) Metrics, (3) Logging policies

References

BICALHO, A. (2019). Achieving 99.99% uptime - a tale of Observability. Retrieved from www.autodesk.com: https://www.autodesk.com/autodesk-university/class/Achieving-9999-uptime-tale-Observability-2019#video