Choreo observability for improved developer productivity

How Choreo observability helps developers to build robust applications


One major challenge of distributed systems is observability. If you are developing a system with 10s, 100s or 1000s of services, then implementing observability at each service so that any failure scenario can be troubleshooted is a tedious task. Developers need to add different levels of logging (e.g. debug, info, fatal, warning) and write code to publish them to log monitoring systems. This would take a considerable amount of time from the developers that would otherwise be spent on doing business-critical implementations.

Choreo methodology

Choreo considers observability as a first-class feature of any enterprise system. Hence it has a built-in observability feature that is enabled by default for each application that you develop. Choreo offers details such as throughput, latency, and logs from the platform itself without any manual interventions from the developers.

The figure below depicts the observability interface of Choreo for a given application.

Figure: Choreo observability feature

Choreo frees the developers from the task of setting up log monitoring systems, adding log entries, and publishing logs from the code. Instead, it provides a built-in observability mechanism that would capture the logs from the underlying infrastructure and monitor them and analyze them and present the details in a user-friendly manner.

Choreo observability provides details such as throughput, latency, log entries, performance breakdown and direct access to the log files. Developers can troubleshoot the errors and failures from the production environment itself by analyzing the provided details and the log files. In a typical enterprise setup, developers spend a lot of time recreating production failures in pre-production environments since they are hesitant to touch the production systems. With Choreo, developers don’t need to worry about those aspects since availability levels are guaranteed from the platform itself.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Chanaka Fernando

Chanaka Fernando


Writes about Microservices, APIs, and Integration. Author of “Designing Microservices Platforms with NATS”