Before the start of the project, log data was scattered in files, databases or in the working memory of individual applications. This meant that error analyses took a long time, as developers first had to find out where the relevant logs were stored. Each application used its own procedures – sometimes files, sometimes databases, sometimes pure in-memory logs.
This fragmentation led to a high level of dependency on individual developers. If a responsible person was absent, error diagnosis was considerably delayed. At the same time, undetected system failures caused expensive downtime: If several employees were unable to work due to missing applications, costs and productivity losses were incurred.
In addition to monitoring availability with Uptime Kuma (➔ to the case study ), central logging covers root cause analysis and makes fault diagnosis much faster.
With a central logging system based on Kafka, jovoco pursued the goal of capturing logs in real time, standardizing them and making them searchable. This allows errors to be detected more quickly, development costs to be reduced and operational failures to be avoided.
Your decision would be the same as that of renowned companies:
