An universal way on how to collect logs in EKS clusters

Summary: Vlad Solodkyi provides a detailed guide on collecting logs in EKS clusters with Sisense. The guide outlines prerequisites, including access to the control plane and Sisense web UI permissions, and provides step-by-step instructions for log collection and access through the Sisense web UI. The steps include connecting to the control plane, copying log files to temporary locations, and accessing them via Sisense. The guide aims to simplify requesting logs for troubleshooting and analysis without customer involvement. For further help, Sisense Support is recommended.

Introduction

This guide provides step-by-step instructions on how to collect logs in EKS clusters. By following these steps, logs will be copied to a storage location accessible through the Sisense web UI. This approach avoids the need to explain the process to customers, making it more convenient to request logs for troubleshooting and analysis.

Prerequisites

Access to the control plane to execute kubectl commands.
Appropriate permissions to access Sisense web UI.

Steps

1. Connect to the Control Plane

Before executing any kubectl commands, ensure that you are connected to the Kubernetes control plane.

2. Copy the .log file to a Temporary Location

Execute the following command to copy the desired *.log file to a temporary location:

kubectl exec -it -n sisense $(kubectl get po -n sisense -l k8s-app=fluentd -o custom-columns=":metadata.name") -- cp /var/log/sisense/sisense/identity.log /tmp/identity.log

3. Copy the .log File from the Temporary Location to the Current Directory.

After copying the log file to the temporary location, use the following command to copy it from the temporary location to the current directory:

kubectl cp -n sisense $(kubectl get po -n sisense -l k8s-app=fluentd -o custom-columns=":metadata.name"):/tmp/identity.log ./identity.log

4. Copy the .log File to the Storage Folder

Now, copy the *.log file from the current directory to the storage folder, which is accessible from the Sisense web UI:

kubectl cp -n sisense ./identity.log sisense/$(kubectl get pod -n sisense -l app=management -o jsonpath='{.items[0].metadata.name}'):/opt/sisense/storage/identity0930.log

Note: In the above command, replace /var/log/sisense/sisense/identity.log in the first step with the desired log file name, and change identity0930.log in the latest step with the desired log file name.

5. Access Logs from Sisense Web UI

The identity0930.log file is now copied to the storage location and can be accessed and downloaded from the Sisense web UI. Follow these steps to access it:

Log in to the Sisense web UI.
Navigate to the "Admin" tab.
Select "System Management" from the options.
Click on "File Management."
Look for the identity0930.log file and access or download it as needed.

Additional Notes

In the steps above, we copied the identity.log file and named it identity0930.log in the last step. You can adjust the naming convention as required.
Remember to replace the filename in the commands with the desired log file name when working with different logs.

Conclusion

Following the steps outlined in this article, you can efficiently request logs from customers using Sisense without the need for them to find and access the logs manually. This streamlined process enhances troubleshooting and data analysis capabilities within Sisense for a more effective and seamless experience.

Should you require further assistance, kindly reach out to Sisense Support.

Vlad Solodkyi

Posted 3 years ago

0 comments