# Monitor Events

## Logs

After installation, you may want to trigger some traffic to one of your services and access it via the ingress protected by open-appsec. You can then run these command to view open-appsec logs:

{% tabs %}
{% tab title="Ingress NGINX" %}
Note the name of the ingress nginx pod by running:

```bash
kubectl get pods -n appsec
```

Show the logs of the open-appsec agent container by running:

```bash
kubectl logs [ingress nginx pod name] -c open-appsec -n appsec
```

{% endtab %}

{% tab title="Kong Gateway" %}
Note the name of the Kong pod by running:

```bash
kubectl get pods -n appsec
```

Show the logs of the open-appsec agent container by running:

```bash
kubectl logs [kong pod name] -c open-appsec -n appsec
```

{% endtab %}

{% tab title="APISIX Gateway" %}
Note the name of the APISIX pod by running:

```bash
kubectl get pods -n appsec-apisix
```

Show the logs of the open-appsec agent container by running:

```bash
kubectl logs [apisix pod name] -c open-appsec -n appsec-apisix
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
ith the default policy logging is done to stdout, so you can easily direct it with fluentd/fluentbit or similar to logs collector (ELK or other). It is possible to configure AppSec to log also to sysconfig.  
{% endhint %}


---

# 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.openappsec.io/getting-started/start-with-kubernetes/monitor-events.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.