# Log Solution

**Log Solutions** help you proactively manage and respond to common issues detected in your app logs. A Log Solution defines how specific log messages should be handled during log analysis, making it easier to filter out known noise, highlight important issues, and guide users toward resolving problems.

Log Solutions are available from two sources:

* **Central Solutions** — created and maintained by **Blue Storm** and pulled from the central repository.
* **Custom Solutions** — created by your **Platform Administrators** to address organization-specific log patterns. (Note: App-specific log processing rules can be created from the App page for a specific app)

#### Viewing and Managing Log Solutions

Navigate to the **Log Solutions** tab in the Repository page to:

* View both **central** and **local (custom)** solutions.
* Create new custom solutions by clicking the **"Add Solution"** button.

#### Creating a Log Solution

When adding a new solution, the following fields and options are available:

* **Title**:\
  Provide a clear and descriptive title for the solution. This will appear when a log message is matched.
* **Enabled**:\
  Choose whether the solution is active for log analysis.
  * **Enabled**: The solution is used to analyze logs and match relevant messages.
  * **Disabled**: The solution is ignored during analysis and won’t match any messages.
* **Description**:\
  A rich-text field where you describe:
  * What this solution matches
  * Why the log message is important
  * Recommended steps to investigate or resolve the issue
* **Log Node**:\
  Specify the log node the solution applies to. This helps narrow down the match to relevant components of your app.
* **Match String** (Regex):\
  Provide a **Java-compatible regular expression (Regex)** to define which log messages this solution matches.
  * To match the content of a **multi-line log message**, begin your Regex with: `(?s)^`
  * Example: `(?s)^.*Database connection lost.*`
* **Action to Take**:\
  Define what happens when a log message matches this solution:
  * **Ignore** — The log message is flagged as *Ignored* and will **not** count towards log level totals (Errors, Warnings, etc.).
  * **Alert** — An *Alert* is sent to the App Administrator for immediate attention.
  * **Solution** — The log message is flagged as *Solution Available*, linking it directly to this solution and its description for easy reference during analysis.

#### How Log Solutions Improve Log Insights

Once created, Log Solutions are automatically applied during log analysis. Matching messages are flagged based on the defined action, helping you:

* Reduce noise by ignoring known, non-critical messages
* Surface critical issues that require immediate attention
* Provide guidance and context directly from the logs for faster troubleshooting

Platform Administrators can edit, enable/disable, or remove custom solutions at any time. Central solutions are managed by Blue Storm and updated regularly to cover common platform issues.


---

# 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.bluestorm.io/administration/system/repository/log-solution.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.