Looking for maintainer(s)

[mivano]

Hi 👋

When I was introduced to Serilog, I was hooked to this idea of structured logging. The possibilities, combined with NoSQL stores, SaaS solutions and even relational databases to store and search events was impressive. I submitted a couple of sinks, like MSSQL, ELMAH, Loggly, RayGun but also the most interesting one; Elasticsearch.

At that time (2014) I was using ES for other projects as well. So it was a great fit to store logs in (back in the times that everything was in private datacenters) and make it searchable with Kibana.

From 2014 to now; we went from many contributors, many changes and many supported .net versions to 43.7M NuGet downloads. But also around 80 open issues, 20 PRs and no active maintainers.

Not only is my time limited (which most likely applies to all of us), but my knowledge about ES is limited as well. The last time I used ES, it was version 2.0. This means I m totally out of the state of affairs with ES or even using this sink myself to store events. It is hard for me to answer any questions, assess proposed changes and keep up to date with the desired direction the sink needs to go to.

So I m looking for 1 or 2 maintainers willing to pick up the responsibility of taking care of this sink. Long long time ago, we had some plans (#254) which can still be valid, but need a revival. The issue list and PR list need to be under control and decisions need to be made which ES version (and .NET versions) are to be supported.

So do you use this sink regularly, preferably already did some work on it and want to be part of the future of this sink, then please let me know!

[Mpdreamz]

Hi 👋 !

Just a heads up that the .NET team @elastic have created our own new Serilog Sink Elastic.Serilog.Sinks:

Package: https://www.nuget.org/packages/Elastic.Serilog.Sinks#readme-body-tab

Documentation: https://www.elastic.co/guide/en/ecs-logging/dotnet/current/serilog-data-shipper.html

As one of the semi maintainers of the original sink in this repository Serilog.Sinks.Elasticsearch and as the drafter of the future plans for Serilog.Sinks.Elasticsearch in #254 I definitely did not take the decision to move our initial efforts for this sink into a new sink owned by Elastic lightly.

• The new Elastic.Serilog.Sinks sink is fully supported by the .NET team @elastic.
• The new sink has a reduced scope
  • Only one way to send logs as ECS logging json. This ensures best interoperability with the rest of Elastic's logging ecosystem.
  • As ECS has been contributed to OpenTelemetry and OTel semantic conventions and ECS will continue to merge this standard will be the lingua franca of the observability and security space well into the foreseeable future.
  • No durable mode, we believe using our serilog EcsTextFormatter and Serilog.Sinks.File + dedicated file based shippers are a better durable architecture.
  • Of course Elastic.Serilog.Sinks still fully supports live log shipping though!
    • In fact this new sink is built upon a completely new way to push (.NET) data into Elastic: https://github.com/elastic/elastic-ingest-dotnet
• Elastic.Serilog.Sinks will not only target Elasticsearch.
  • Long term we will explore it sending data to our APM product, OTLP, Logstash, Elastic Agent and many others.

I encourage everyone to try out this new sink and report questions/bugs to https://github.com/elastic/ecs-dotnet 👍

[mivano]

That is great news @Mpdreamz ! Good to say goodbye to some of the elements in the current sink that served well over the years, but became hard to maintain and support.