log elastic mapping errors as errors in elasticsearch

[pierresetteskog]

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or
community projects.
This issue list is intended for Serilog Elasticsearch Sink issues. If this issue relates to another sink or to the code project,
please log on the related repository. Please use Gitter chat and Stack Overflow for discussions and questons.

Does this issue relate to a new feature or an existing bug?

• Bug
• New Feature

What version of Serilog.Sinks.Elasticsearch is affected? Please list the related NuGet package.

What is the target framework and operating system? See target frameworks & net standard matrix.

• netCore 2.0
• netCore 1.0
• 4.7
• 4.6.x
• 4.5.x

Please describe the current behavior?
Its easy to by accident log same field with different datatypes and get errors like:

Received failed ElasticSearch shipping result 400: {"type":"mapper_parsing_exception","reason":"failed to parse field

And its easy to miss errors in selflog
Please describe the expected behavior?
It would be nice if all not connection error problem was logged as errors in elasticsearch as string.
Or at least the excption is also sent to Action<LogEvent,Exception> ElasticsearchConfiguration.FailureCallback

If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

[mivano]

I do see what you mean, due to the batching and background work, it is difficult to spot issues. it is also not an audit sink, so exceptions are hidden. The use of the EmitEventFailureHandling option might be useful here?

[mivano]

Old issue, cleaning up. Still facing this issue, feel free to reopen.