Install Log Service

Log Service uses 'OpenSearch' to provide log storage and an API server to communicate with Cocktail Dashboard.

Before installing the log service, 'cert-manager' and 'nginx' require pre-installation.

1. Distribution Addon

1) Infrastructure - Clusters - Addon List - Click the "Deploy" button and click the "Deploy" button for 'cocktail-log-service' in the list.

2) Check the settings according to your environment and click the Deploy button to deploy the Addon.

Gateway Service Mode : Log service gateway type (Ingress, LoadBalancer)

---

[If Gateway Service Mode is set to Ingress]

Gateway Access URL : DNS to access log service through Ingress

URL Type : Cluster HostAliases type (PublicDNS or HostAliases)

Host Ip : (If URL Type is 'HostAliases') LB IP (or node IP) that can access the cluster from outside

When accessing the log service from the dashboard or collecting logs from log-agent, connect the Host IP to the Log Access URL.

Enable OpenSearch Dashboard : Use or not 'Opensearch Dashboard'

---

[If Gateway Service Mode is set to LoadBalancer]

Clusters created through provisioning can only be set to 'Enable OpenSearch Dashboard'.

3) Check the deployment status and if the status is 'Running', confirm that the deployment has been completed successfully.

If the status is 'pending' when deployed

Troubleshooting | Cocktail Cloud Online

4) Create a job in the namespace where the log service is installed.

Create a Job that creates policies for each container log, cluster audit log, and application log collected by Opensearch.

apiVersion: batch/v1
kind: Job
metadata:
  name: policy-generate
  namespace: cocktail-logs
spec:
  ttlSecondsAfterFinished: 600
  template:
    spec:
      containers:
        - image: [registry address]/library/cocktail-auto-injector:1.0.0-release.20240425
          imagePullPolicy: Always
          command:
            - /bin/sh
            - -c
            - sh /auto/service/gen.sh -H opensearch-cluster-master.cocktail-logs -c 30d -u 100d -a 30d -m run
          name: gen
      restartPolicy: Never
  backoffLimit: 0

registry address : Please contact our technical team.

If you create a job according to the settings above, container logs have a storage period of 30 days, cluster audit logs have a storage period of 56 days, and application logs have a storage period of 1 year.

Storage period settings can be modified in 'OpenSearch Dashboard'.