> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md).

# Investigate system logs

The project's error logs history is stored here. Error logs help you to efficiently identify the problems and errors occurred in your project.

Use system logs to investigate messages associated with app or integration problems.

## Find relevant messages

1. Open **More → System logs**.
2. Set **Date from** and **Date to** around the reported problem.
3. Narrow **Level**, **Source**, or **Action** as appropriate.
4. Use **Search logs** for a relevant term.
5. Review the source/action, message, and date of matching entries.

![System logs with Level, Source, Action, date filters, Search logs, and an empty result](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FoTkheDIODi1orMCgVaUK%2F09-system-logs.png?alt=media)

The screenshot shows an empty result. **Nothing found** means no entries matched the current view; it does not prove that the underlying operation succeeded.

## Troubleshoot an empty result

Check the app and environment, widen the date range, and remove unnecessary filters. Reproduce the issue with test data and note the exact time. If no relevant entry appears, investigate the identity provider, API, or resource involved as appropriate.

## Share useful diagnostics

Include the symptom, reproduction steps, approximate time with timezone, and redacted relevant message. Remove tokens, passwords, cookies, and customer data before sharing.

Use [the audit trail](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md) for available user activity. Use [sign-in troubleshooting](/access-and-sharing/authentication-and-sso/troubleshoot-sign-in.md) when the issue occurs during authentication. Confirm retention and coverage for your deployment rather than assuming logs are permanent.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.