IMPLEMENTATION OF OBSERVABILITY DESIGN PATTERN IN ENTERPRISE SOFTWARE

Abstract

ABSTRACT

The purpose of this article is to present a standardized improvement in the messaging of information log records, alerts and errors, through the implementation of software that is responsible for displaying the information in a friendly way to the end user, to generate alerts or necessary statistics. for decision making, whose title is Implementation of an Observability design pattern in Enterprise Software. Based on the background of Erich Gamma (1994) for the conceptualization of patterns, NewRelic (2024) on aspects of the latest technologies and Google in 2014 who introduces the concept of observability. On the methodology side, it is based on Hernández, Fernández and Baptista (2010) as a feasible project type, with a descriptive basis and correlational research, being useful for a software technological implementation project. The population was the group of sponsors, development team, architecture team, project team and prospective clients of the Kapsch TrafficCom company, and the prospective clients who acquired the Kapsch TrafficCom product, since the software product seeks to satisfy the particular needs in the management of concessioned highways. In relation to the main results, according to the company's security policy, any project must ensure the stability and resilience of the technological components to be implemented. Any security breach triggered by a new implementation will have a high impact. Likewise, there are pieces of software that are critical for the company and due to the language in which they were developed, there is no possibility of implementing monitoring with design patterns without them. However, this opens the possibility of migrating or creating new software modules that replace the previous ones with the appropriate programming language. Finally, in any software implementation there must be a testing period to ensure the quality of the deliverable, either at the end of the complete development of the software or at the end of the incremental partial deliveries that are developed in the Agile methodology. With this we ensure that our deliverable is functional, meets what was requested and satisfies the client's main needs. Although there are ways to recover exceptions and collect errors in terms of log files or directly in a database, the human resource or knowledge to obtain it is not always available. That is why the implementation of the OpenTelemetry framework and the Observer design pattern in the organization's applications was essential.