ᐅ Are there alternatives to MALM for common issues?

Are there alternatives to Malm for common issues?

I have been using MALM for some time across several projects, but I keep encountering recurring problems, especially regarding implementation stability and performance bottlenecks in larger applications. Therefore, I am wondering if there are well-established alternatives to MALM that are more robust or efficient in handling these issues. It would be important to find tools or frameworks that offer similar functionality but potentially scale better or allow for simpler error management. I look forward to your experiences and recommendations.

Yes, there are alternatives like Serilog or NLog, which are often used as replacements for MALM. Both offer more flexible configuration and greater stability in large systems.

To clarify your question further: MALM is primarily known as a logging framework, right? If so, you should take a closer look at alternatives like NLog, Serilog, or log4net.

1. NLog offers a wide range of targets and is very performant.
2. Serilog is designed for structured logging, making filtering and analysis easier.
3. log4net is quite old but stable and widely used.

Common issues with MALM could include bypasses due to asynchrony and event loss, whereas Serilog works well with a robust sink system.

Conclusion: The best tool depends heavily on your specific use case, for example, whether you want JSON-based logs or more traditional file logging.

Have you already checked the MALM documentation to see if the issues can be resolved with an update?

Alternatively, Serilog and NLog are good options that are actively maintained.

Leandrop57 schrieb:
regarding the stability of the implementation and performance bottlenecks in larger applications

Both are commonly reported issues, but before looking for an alternative, it is important to measure precisely where MALM fails. In many cases, I have observed that incorrect configurations or excessive logging are the main reasons, rather than the framework itself.

If alternatives are still being considered, it is worth comparing the architecture: MALM is heavily event-driven, while Serilog focuses more on structured event data. Which one performs better depends on the specific application.

Could you please provide more detailed information about your setup? Which platform, versions, and what kind of logs are you generating?

Thanks first of all for your responses.

Regarding dinano’s follow-up question: I am working with MALM in a .NET Core environment, currently version 2.1, in a microservice setup with a lot of asynchronous communication. The logs mostly consist of status and error codes, sometimes with extensive contextual data (user actions, etc.).

The problem mainly occurs during peak loads: MALM sometimes loses log entries or the service performance noticeably degrades.

Could an alternative provide sustainably better performance in this situation, or are these limitations inherent to any solution handling similarly high volumes?