# Logs

Logs, being one of the core features of the Insights panel, are a great help when identifying potential errors in your flow, or generally checking the flow performance and data that passed through it. [As you already know from one of the previous sections, you can troubleshoot errors also in a flow](/kb/appmixer-studio-features/troubleshooting-errors.md). This time, nonetheless, we will focus on the "Logs" view in the Insights panel.

First and foremost, let's see where you can find Logs using the Insights panel.

![Logs](/files/-MgKz2KY5LmW_vQ3h0m5)

By default, you'll see Logs for all your flows and for a given time range.

![Time range](/files/-MgKzPVDvCL6AxKIEses)

You can, nonetheless, filter the Logs only for specific flows. To do so, use the search bar on the left.

![Filtering Logs by flows](/files/-MgL2UNVW9jzhjFRcIWM)

Besides the flow data messages histogram represented by the bar chart in the upper part, there are all Logs that allow you to see the performance of your flows in better detail, and identify potential errors. Note that after clicking on any of the Logs, a Log detail pops up giving you more details on the particular data message.

![Log details](/files/-MgL2kh4EPMcuzXX_y5a)

Now that you know how to navigate to Logs either [in a flow](/kb/appmixer-studio-features/troubleshooting-errors.md) or in the Insight panel, [let's explore all the possibilities the Dashboard offers](/kb/appmixer-studio-features/insights/dashboard.md).


---

# 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.appmixer.com/kb/appmixer-studio-features/insights/logs.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.