+972 52-548-6969
RavenDB 7.0 ReleasedMoving to NLog
One of the “minor” changes in RavenDB 7.0 is that we moved from our own in-house logging system to using NLog. I looked at my previous blog posts, and I found the blog post outlining the rationale for the decision to use our own logging infrastructure from 2016.
At the time, no other logging framework was able to sustain the kind of performance that we required. The .NET community has come a long way since then, and it has become clear that we need to revisit this decision. Performance has a much higher priority, and the API at all levels supports that (spans, avoiding allocations, etc).
The move to NLog gives users a much simpler way to integrate RavenDB logs into their monitoring & observability pipeline.
You can read about the new NLog feature in our blog.
We also spent time making the logs view inside the RavenDB Studio nicer, taking advantage of the new capabilities we now expose:
Hopefully, you won’t need to dig too deeply into the logs, but it is now easier than ever to use them.
More posts in "RavenDB 7.0 Released" series:
- (07 Mar 2025) Moving to NLog
- (05 Mar 2025) Snowflake & data warehouse integration
- (03 Mar 2025) AWS SQS & AWS Lambda integration
- (27 Feb 2025) AI & Vector Search
Comments
Can you explain the reasoning for choosing NLog over other solutions, such as log4net/Serilog?
Why not Serilog? Seems to be the "goto" logging for me at the moment
Two primary factors here. First of all, the knowledge and confidence, we are utilizing NLog in a lot of internal projects and we are familiar with its strengths and capabilities. This allowed us to deliver the solution faster, because we knew, with all the extensibility features, that it can substitute our custom logging and do even more.
At the end, the primary goal was to give users the capability to connect our logging system to external logging aggregators, and the amount of plugins that NLog has is very vast. Second of all, we tested it against our logging and NLog team did a great job in utilizing the machine resources. At the end, it was a reasonable choice. At any point we are not saying that log4net and/or Serilog would also not be a great choice, but we went with NLog.
Comment preview
Join the conversation...