> For the complete documentation index, see [llms.txt](https://cocktailcloud.gitbook.io/cocktail-cloud-online-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cocktailcloud.gitbook.io/cocktail-cloud-online-en/log-service/build-server.md).

# Cocktail Log Service

It plays an important role in operations and troubleshooting, managing the containers and logs running in the cluster.

## 1.  Cocktail Log Service

1. **Collect logs for all resources within the cluster.**

* Collects all containers and audit logs within the cluster.
* Collect application logs for workloads that exist in the cocktail.
* In the case of application logs, only authenticated applications can be checked.
* Collected using open source 'Opentelemetry' and 'Opensearch'.

2. **Provide a service that searches and analyzes collected logs.**

* Collected logs can be analyzed by filtering them with labels.
* Collected logs are aggregated by time so users can analyze log trends.
* Can search and analyze collected logs.

## 2. Recommended specifications

#### This guide is based on installation on an 8Core 16GB node.

* master node : 1Core, 2GB
* data node : 2Core, 4GB
* dashboard : 500mCore, 1GB

## 3. Architecture

<figure><img src="https://4196990571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5As9l8R3RbLkQd6XsfL%2Fuploads%2FGMTZ2TrtgRsOoZSUuwQa%2Fimage.png?alt=media&amp;token=d1f47159-74e7-4e39-a76a-e640e162f4ad" alt=""><figcaption></figcaption></figure>

Effectively manage cluster containers and application logs to increase operational efficiency and ensure system stability. The following provides guidance on how to collect logs for each log screen and application.