[WSO2Con Asia 2018] Tooling for Observability
By Vichitra Godamunne
- 10 Aug, 2018
Nowadays, Observability has become a hot topic in the software industry. Observability, a term that comes from control theory, is a measure of how well internal states of a system can be inferred from knowledge of its external outputs.
There are many monitoring tools which let you know whether a system is functioning as expected. However, with observability, we can find an answer to the question of why a system is not functioning the way you want. In this sense, monitoring is just a subset of observability. Instrumentation also plays a principal role in making your system observable. For instance, the use of logging in systems (especially structured logging), collecting metrics in the runtime such as request count and response time, and the use of unique IDs for requests in order to do distributed tracing, are vital instrumentation techniques for observability. As a matter of fact, logging, monitoring and distributed tracing are considered as the three main ways to provide the observability in a system.
This session will focus on the observability of WSO2 products, the tools for observability and how WSO2 will make its next generation products observable by default using well-known standards like OpenTracing specification.
Sinthuja has been part of the WSO2 team for nearly 7 years. She has been closely working with and engaging in the design and development of various WSO2 products including WSO2 Data Analytics Server, WSO2 Dashboard Server, WSO2 IoT Server, and now Ballerina. Currently, she mainly focuses on the observability and governance aspect of Ballerina and other WSO2 products. She has also participated in and led multiple customer engagements, such as Quick Start programs and architecture reviews, and assisted in defining the solution architecture for multiple industries.