> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/insights/logs.md).

# Logs

The **Logs** tab provides a detailed overview of log messages per log level (such as Error, Warning, or Info) for each app and environment on the selected day. This helps you quickly identify where most log activity is happening and focus on potential issues.

From the **first-level summary** (log level totals per environment), you can drill down to the **second-level summary**, where log messages are aggregated by **log node** within the selected environment. This view helps pinpoint which component of your app is generating specific logs.

Clicking on a **log node** opens the **log message view**, where you see all individual log messages generated by that node. Each message includes additional status indicators that provide more context:

* **Ignored** – the message is excluded from log level totals and doesn't contribute to error or warning counts.
* **Alert** – an alert has been generated based on this message.
* **Solution available** – a suggested solution is available for review and action.

You can also see **why** a message is flagged as Ignored, Alert, or Solution—either because of a **log processing rule** or because a **solution has been linked** to it.

Additionally, you can **export** log messages or summaries at every level—environment, log node, or individual log message—for further analysis or sharing.

> **Note:** Ignored messages do **not** count toward the log level totals (e.g., Errors, Warnings), providing a clearer and more focused view of your log data.

This drill-down flow—from environment summary to log node to individual log messages—allows you to efficiently investigate logs, understand the context of alerts, and act on available solutions.


---

# 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.bluestorm.io/dashboards/insights/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.