Would you like to reduce your ticket exchange by up to 20 minutes? Are you doing well with ticket changes? Wouldn't you like to focus on selling new tickets and increasing the productivity of your business at that time? If so, it's time to think about introducing an automated process that will do it for you.
In the past, when most applications were built in monolith architecture, surely some of you remember how you managed logs. The application was deployed on a few servers, and in a case when some errors occurred, usually the logs were downloaded and searching errors e.g. via grep tool, within all log files from all servers. Currently, when systems are built mostly as distributed systems (microservices, cloud-native, etc), the more sophisticated approach of log managed is needed.
These days, systems are more and more distributed, usually build in microservices architecture or serverless architecture. Services are built with different languages, frameworks, running on the cloud, frequently running within the containers, deploying at least two replicas for high availability. A system can be built with hundreds or even thousands of components. That's why the observability is one of the most important parts of the solution.