General

Before the ODJ, people relied on traditional ways to receive transparency over their application development. In many cases, providing relevant information was not the focus of software and other tools that were required to develop applications (e.g. dev tools, infrastructure, security). This means that staying updated when it comes to application development, required additional tools or other efforts and was mainly an individual’s responsibility to ensure. Also, since all those tools and services where not provided by the same source (such as ODJ), application teams simply didn’t have the capability to receive all information required at one central place. At least, not per “default” and without a lot of costs and effort.

The ODJ is providing a large set of services and tools around its automation capabilities. By using the ODJ, we provide information in regards everything that is used across the journey. Additionally, it ensures that further relevant information, such as organization related input for example, is managed as well.

ODJ looks at transparency from an different angle compared to traditional monitoring. It aims to provide all the transparency required to successfully build applications in a cost efficient, stable and measurable way. Transparency doesn’t stop at cost level. Mostly, other metrics that at long last, imply an increase in costs, such as the consumption of services increasing, the quality of services/applications decreasing, a bad code quality or simply human mistakes. Having all this information at one place allows a more holistic view on transparency, but furthermore provides the capability to correlate data. This allows more in depth view and further insights.

In the following, some of the different metrics categories provided by the ODJ are further elaborated. If you are familiar with the overall metrics, you can view advanced information.