# Logs & Profiling

{% 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.

1- [**Repro Steps**](/android/set-up-luciq-for-android/logs-and-profiling/repro-steps-for-android.md)\
Trace your users steps visually with simplified logs, grouped by screenshots.

2- [**Session Profiler**](/android/set-up-luciq-for-android/logs-and-profiling/session-profiler-for-android.md)\
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.

3- [**Report Logs**](/android/set-up-luciq-for-android/logs-and-profiling/report-logs-for-android.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.


---

# Agent Instructions: 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.luciq.ai/android/set-up-luciq-for-android/logs-and-profiling.md?ask=<question>
```

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.