# 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`.

<figure><img src="/files/QqsEG2QVBjDHFnJVLT3J" alt=""><figcaption></figcaption></figure>

2. 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.

<figure><img src="/files/d8l5E12w1Rqv3ReSZuO3" alt=""><figcaption></figcaption></figure>

3. 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](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-ssh.html).

<figure><img src="/files/levrwRQt9QHZXlI5DdNs" alt=""><figcaption></figcaption></figure>

4. 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.

<figure><img src="/files/3nio2iUk8Q9AdhoSwlSk" alt=""><figcaption></figcaption></figure>

5. 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.

<figure><img src="/files/IU8aBDkC0tM6KohLFKAx" alt=""><figcaption></figcaption></figure>

## 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.

<figure><img src="/files/SRkVVVSZzaTXvqgYiCJq" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/w0AjFsXx06PXpsp8VTdu" alt=""><figcaption></figcaption></figure>

4. 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.

<figure><img src="/files/WS4f25zbZNCLW3PPWNGZ" alt=""><figcaption></figcaption></figure>

## Local deploy using docker

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

<figure><img src="/files/QbqsLhpVe6RU9u9WHtsa" alt=""><figcaption></figcaption></figure>

2. 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.

<figure><img src="/files/ndj9S7r2Oda1CPoJCJGQ" alt=""><figcaption></figcaption></figure>


---

# 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://docs.akto.io/troubleshooting/logs.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.