BAM Log Configuration

The Ometa framework's extensive logging feature, BAM, has evolved over the different releases attempting to make it easier to set up and configure. Additionally, the BAM configuration and internal log processing have been adapted to fully adhere to the latest logging practices currently in use in the software industry.

In this section, detailed information about the following items can be found:

• Appsettings.json Configuration
• Initialisation Fallback
• Automatic Reload Configuration
• Troubleshooting

Important

Only the described functionality and feature set in this section will remain backwards compatible in future releases.

Any other non-documented part currently present in the BAM logging system may be subject to change in upcoming releases. Using those elements in a portal solution is at your own risk as an update to a later version of the Framework may cause breaking changes.

Migration To New Structure

The Ometa framework versions before v5.x used a different setup and configuration style for BAM logging. An upgrade of the framework to v5.x has an impact on the previous existing configuration.

Please consult the article Old Configuration Migration for full information in case of a framework upgrade.