Thanks for visiting this category strategy page on Logging in GitLab. This category belongs to and is maintained by the APM group of the Monitor stage.
This strategy is a work in progress, and everyone can contribute:
A fundamental requirement for running applications is to have a centralized location to manage and review the logs. While manually reviewing logs could work with just a single node app server, once the deployment scales beyond one you need solution which can aggregate and centralize them for review.
Being able to capture and review logs are an important tool for all users across the DevOps spectrum. From pure developers who may need to troubleshoot their application when it is running in a staging or review environment, as well as pure operators who are responsible for keeping production services online.
The target workflow includes a few important use cases:
In the distributed nature of cloud-native applications, it is crucial and critical to collect logs across multiple services and infrastructure, present them in an aggregated view, so users could quickly search through a list of logs that originate from multiple pods and containers. Therefore, our next step allows our users, with a push of a button to install Elasticsearch on their monitored cluster and collect automatically, all logs from all namespaces in the cluster to facilitate an aggregated logging solution. This enhances our logging capabilities and offers advanced filtering and a full-text search across aggregated logs in a single view.