If for some reason we are not able to log may be due to connection issue or any other problem there should be a Fallback as wit is available in Serilog.Sinks.Elasticsearch.
Since you Elastic team is encouraging to use their sink then it should have atleast basic features.
If for some reason we are not able to log may be due to connection issue or any other problem there should be a Fallback as wit is available in Serilog.Sinks.Elasticsearch. Since you Elastic team is encouraging to use their sink then it should have atleast basic features.
There should be a reconnect/retry mechanism.
ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog):
ECS schema version (e.g. 1.4.0):
ECS .NET assembly version (e.g. 1.4.2):
Elasticsearch version (if applicable):
.NET framework / OS:
Description of the problem, including expected versus actual behavior:
Steps to reproduce: 1. 2. 3.