How to get logs

You can deploy Akto on multiple platforms like AWS, k8s etc. Please follow the below guide to find logs on your respective platform.

AWS using Auto scaling group

1. If you've deployed Akto on AWS using an auto scaling group, log in to AWS console and go to EC2 dashboard.

1. If you have to get dashboard logs, then go to Auto scaling group and find the AktoDashboardAutoScalingGroup auto scaling group. For runtime logs, go to Auto scaling group and find the AktoAutoScalingGroup auto scaling group.

1. Find the associated EC2 instance in Instance management tab and SSH inside that instance. To SSH inside the instance, you can refer to this AWS guide.

1. Login as the root user using sudo su - and run docker ps to find the running containers. For dashboard logs, look for akto-api-security-dashboard container. For runtime logs, check for the container with runtime word it.

1. You can find the logs for any container using the following command docker logs <container-id> --tail 10000 . Since there can be many logs, we are using --tail 10000 , you can increase this number for older logs or add -f flag for running logs.

Using helm charts in kubernetes

1. Connect to your kubernetes cluster

2. Check your deployments for an akto deployment using kubectl get deployments -n <namespace>. Make sure the namespace is correct.

1. You can get the pods associated with this deployment using kubectl get pods -n staging.

1. Pick the pod you'd like to view the logs for and run the following command kubectl logs <pod-name> -n <namespace> --tail 10. Since there can be a good number of logs, using tail is recommended. You can also use -f flag for running logs.

Local deploy using docker

1. If you've deployed locally using docker, run a docker ps to check the running containers.

1. Run docker logs <container-id> --tail 100 . Since there can be many logs, we are using --tail 100 , you can increase this number for older logs or add -f flag for running logs.