This epic related to our [Logging Vision page](https://about.gitlab.com/direction/monitor/apm/logging/) This Epic group all related issues and epics require to move Logging from Minimal to Viable ### Problem to solve Applications, operating systems, and programmable or smart devices generate millions of log lines, analyzing those logs are important as it can help troubleshoot systems, computers, or networks, help analysing user behavior security breaches and more, therefore a fundamental requirement from an observable system is to have a centralized location to store manage and search logs. ### Intended users [Devon the DevOps Engineer](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) [Sidney the Systems Administrator](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details At our minimal state, we display logs directly from Kubernetes, we would like to enhance our capabilities with the following. ### Proposal * Deploy Elastic Stack as a managed app into a Kubernetes cluster https://gitlab.com/groups/gitlab-org/-/epics/2028 * Automatically collect application logs https://gitlab.com/gitlab-org/gitlab/issues/33834 * Create a compact display for viewing and analyzing real-tie and historical log data: https://gitlab.com/groups/gitlab-org/-/epics/2114 * Pull logs from Elasticsearch. * Ability to search and get relevant log results quickly. * Infinite scroll to search through log history. * Quickly view logs from every environment, pod, and container directly from Kubernetes https://gitlab.com/groups/gitlab-org/-/epics/2113 ### WIP Design | List view on Operations > Pod Logs | Detail view of individual logs | | ------ | ------ | |  |  | ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references /label feature