# Cocktail Log Service

## 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="/files/Fg2mJTCB6YyFfbrKThqw" 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cocktailcloud.gitbook.io/cocktail-cloud-online-en/log-service/build-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.