Engineering modern large-scale software requires software developers to not solely focus on writing code, but also to continuously examine monitoring data to reason about the dynamic behavior of their systems. These additional monitoring responsibilities for developers have only emerged recently, in the light of DevOps culture. Interestingly, software development activities happen mainly in the IDE, while reasoning about production monitoring happens in separate monitoring tools. We propose an approach that integrates monitoring signals into the development environment and workflow. We conjecture that an IDE with such capability improves the performance of developers as time spent continuously context switching from development to monitoring would be eliminated. This paper takes a first step towards understanding the benefits of a possible monitoring-aware IDE. We implemented a prototype of a monitoring-aware IDE, connected to the monitoring systems of Adyen, a large-scale payment company that performs intense monitoring in their software systems. Given our results, we firmly believe that monitoring-aware IDEs can play an essential role in improving how developers perform monitoring.@en

It is important to detect problems fast and to have a clear overview of what is happening within a system after deployment to maximize the uptime and functional quality of the system. Therefore it is necessary to increase the awareness that developers have of errors and logs. Increasing the awareness that developers have of errors and logs has a positive impact on finding problems and solving them. This thesis aims to use monitoring information to bridge the gap that exists between development and operations. We propose to do this by linking the logs to source code to provide this missing link between development and operations. We provide a theory for a monitoring-aware IDE which aims to tackle some of the challenges and enhance some of the practices that exist in the field. We implemented a monitoring-aware IDE and performed a field study to measure its effect. Our results show that a monitoring-aware IDE assists the developer in understanding the system, fixing problems in the code, and improving the monitoring code.