> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/flutter/setup-luciq-for-flutter/logs-and-profiling.md).

# Logs & Profiling

An overview of the different types of logs can be found in this section along with details regarding the session profiler for your Flutter apps.

{% hint style="warning" %}

#### Privacy Policy

It is highly recommended to mention in your privacy policy that you may be collecting logging data in order to assist with troubleshooting bugs.
{% endhint %}

With each bug and crash report, you can find a whole host of useful logs, as well as a session profiler to help you track your issues further.

{% stepper %}
{% step %}

#### [Repro Steps](/flutter/setup-luciq-for-flutter/logs-and-profiling/auto-masking-and-repro-steps.md)

Trace your users' steps visually with simplified logs, grouped by screenshots.
{% endstep %}

{% step %}

#### Session Profiler

The session profiler shows the state of the device up to a minute prior to a report being sent, which can assist with the bug fixing process.
{% endstep %}

{% step %}

#### [Report Logs](/flutter/setup-luciq-for-flutter/logs-and-profiling/report-logs.md)

Instead of having to reproduce the crash or bug on your device to check the logs, we automatically attach the console logs, the verbose logs, all the steps done by the user until the report was sent, the user events, and the network logs.
{% endstep %}
{% endstepper %}


---

# 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.luciq.ai/flutter/setup-luciq-for-flutter/logs-and-profiling.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.