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:

Ingress NGINX

Note the name of the ingress nginx pod by running:

kubectl get pods -n appsec

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

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

Kong Gateway

Note the name of the Kong pod by running:

kubectl get pods -n appsec

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

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

APISIX Gateway

Note the name of the APISIX pod by running:

kubectl get pods -n appsec-apisix

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

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

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.