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.
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.
Just a quick practical note: I switched to Serilog and implemented the async file concept. Since then, no log entries have been lost, even during peak loads.
The setup required minimal effort, but the benefits are huge. Additionally, integration with ELK was much easier.
So yes, a clear recommendation for an alternative framework if you need the complete package 🙂
The setup required minimal effort, but the benefits are huge. Additionally, integration with ELK was much easier.
So yes, a clear recommendation for an alternative framework if you need the complete package 🙂
Additionally:
That is very true.
Alternatives are not necessarily better if the basic requirements or the logging design are not right.
Leandrop57: What does your entire logging workflow look like? The problem might also be with the log aggregator or the collector.
Sometimes the framework is blamed too quickly, even though the pipeline fails elsewhere.
dinano schrieb:
‘A framework that tries to cover everything at once will never be stable.’
That is very true.
Alternatives are not necessarily better if the basic requirements or the logging design are not right.
Leandrop57: What does your entire logging workflow look like? The problem might also be with the log aggregator or the collector.
Sometimes the framework is blamed too quickly, even though the pipeline fails elsewhere.
L
Leandrop5730 Jul 2018 13:22Very valuable input here, thank you all!
I will implement the async logging with Serilog as a proof of concept and at the same time take a closer look at the telemetry.
What is clear already: Simply switching the framework won't help if the overall setup isn't right.
I’ll keep you updated if there is interest.
I will implement the async logging with Serilog as a proof of concept and at the same time take a closer look at the telemetry.
What is clear already: Simply switching the framework won't help if the overall setup isn't right.
I’ll keep you updated if there is interest.