> 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/app/log-rule.md).

# Log Rule

Log rules are used to automatically scan your app logs for strings of text, and if they match, perform a specific action. Log rules are app-specific and can be access from the Logs tab in the app page. The following describes how to configure an individual log rule:

* **Node.** Enter the exact node name of the log node that should be matched. The name must match exactly.
* **Level.** Enter the log level to match.
* **String to match.** Enter a regex (Java compatible) to use to match the log message. An important point is that some log messages are multi-line. To match the content of a multi-line message you must start your regex with the following: `(?s)^`  An additional tip is that you often need to match the text after the text you are searching for by ending your regex with `.*`
* **Action to take.** What action the system should take when a log message matches this rule. The available actions are:
  * **Ignore.** This log message will me flagged as ignored, and it will no longer count towards error, warning, etc. totals in the log message overview.
  * **Alert.** A log alert will be generated (changes the app status in the dashboard, sends out an alert to the app administrator).
  * **Use Solution.** The log message will be flagged as 'solution available', and this will be visible in the log message overview. This is helpful for app operators to know what they should do.


---

# 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/app/log-rule.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.