> For the complete documentation index, see [llms.txt](https://docs.elementary.io/contributor-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elementary.io/contributor-guide/feedback/reporting-issues/debug-logs.md).

# Retrieving Logs

Many apps will create logs for various types of errors with additional information that a developer can use to locate the source of the issue. Including those logs in your issue reports when you experience a problem can help solve the problem faster.

{% hint style="info" %}
To view existing logs from all your applications you can use [`journalctl`](https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs)\`\`
{% endhint %}

By default, debug messages are not shown since they can be quite noisy in normal usage. To see debug logs, start the app from Terminal using the [environmental variable](https://www.digitalocean.com/community/tutorials/how-to-read-and-set-environmental-and-shell-variables-on-a-linux-vps) `G_MESSAGES_DEBUG`

```bash
G_MESSAGES_DEBUG=all com.github.myteam.myapp
```

If the app in question is a Flatpak app, like the apps available from AppCenter, you'll need to start the app with `flatpak run` as well:

```bash
G_MESSAGES_DEBUG=all flatpak run com.github.myteam.myapp
```

Now that logs are being printed to Terminal, reproduce the issue you're experiencing then copy and paste the Terminal output to the bottom of your issue report.

{% hint style="info" %}
For information on creating logs in your app, see the [developer guide](https://docs.elementary.io/develop/writing-apps/creating-logs)
{% 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, and the optional `goal` query parameter:

```
GET https://docs.elementary.io/contributor-guide/feedback/reporting-issues/debug-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.