If you install the log agent, you can check the collected container logs and audit logs on the cocktail dashboard.
1) Infrastructure - Cluster - Addon List - Click the "Deploy" button and click the "Deploy" button for 'cocktail-log-agent' in the list.
2) Check the settings according to your environment and click the Deploy button to deploy the Addon.
Enable Container log collecting : Whether to collect container logs
Enable Audit log collecting : Whether to collect cluster audit logs
audit-log hostPath path : If it is not a cluster installed with 'cube', you will need to change the path.
includeNamespace : List of collection processing namespaces
If you are collecting container logs for a specific namespace, uncomment and use below.
Log Operator is an Addon required when using automatic container log measurement among application log collection methods.
1) Infrastructure - Clusters - Addon List - Click the "Deploy" button and click the "Deploy" button for 'cocktail-log-operator' in the list.
2) Check the settings according to your environment and click the Deploy button to deploy the Addon.
3) Check the deployment status and if it is Running, confirm that the deployment has been completed successfully.
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) 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
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.
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'.
You can collect and analyze each log by installing and registering a log service in your cluster.
Only one log service installed on the platform can be registered.
1) Settings - Basic Information, click the selection box for the log service name to view the list of installed log services.
2) Specify the log service you want to register and click the “Register” button to register it on the platform.
When changing the log service, simply select a different log service from the list and click the "Register" button to change it.
You can discontinue the log service function registered on the platform by clicking the “Deregister” button.
