# Troubleshooting ## No Container Logs * Check that the app emits logs and annotation is present * Check index name and provided api\_key are correct * Check logstash pod logs ```bash kubectl -n logs --tail=200 ``` ## No Audit Logs * Ensure query is correct, referring to the fields reference for kubernetes audit logs * Check index name and provided api\_key are correct ```bash kubectl -n logs --tail=200 ``` ## Logstash Pod Issues * Describe pod for errors: ```bash kubectl -n describe pod ``` * Check cluster events ```bash kubectl -n get events --sort-by=.metadata.creationTimestamp ``` {% hint style="success" %} **Notes** * Export logs: Use logstash to export logs to your existing platform. * Log retention: By default, logs are retained for 30 days or 50 GB (whichever comes first). * Collect both audit & container logs: Yes, enable container logs as described above. Audit logs enabled by default. * Support: Open a [ticket](/guidance-for-individual/service-portal-ai/ticket.md) in the Service Portal AI. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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.cloudeka.ai/guidance-for-individual/deka-gpu/deka-gpu-log-collection/troubleshooting.md?ask= ``` 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.