AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
      • Log Rule
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
        • Log Solution
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Administration
  2. System
  3. Repository

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.

PreviousRepositoryNextProduct License

Last updated 1 month ago