Concerns About the Future of This Repository

[alaeddineG]

Looking at the history of this repository, I’m wondering if it still has a future.

I’m using this sink in a production environment to buffer logs from hundreds of clients to Event Hub and then to Elasticsearch (for various reasons). However, I have some concerns regarding its performance and maintainability. Upon reviewing the code and its dependencies, I’ve identified several areas for improvement:

Dependency Updates:

• Serilog.Sinks.PeriodicBatching is obsolete and should be replaced with IBatchedLogEventSink.
• The repository uses an outdated version of Serilog.
• It also relies on an older version of Azure.Messaging.EventHubs.

Batch Configuration:

• The batch limit of 100 is arbitrary. Event Hub imposes a size limit on batches, not a count-based limit.

Modern Authentication:

• There is no support for Azure Identity, which forces the use of connection strings.

Community Engagement:

• Several PRs are still unmerged/unapproved, with no feedback provided.

This question might seem redundant, as someone has already raised a similar concern here. However, my main question is: What’s next for this repository?

Should we expect future updates or consider looking elsewhere for alternatives?

Looking forward to your feedback.