This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 196
Log events don't arrive in Elasticsearch with {@Property} in the Messagetemplate #47
Comments
Now I've an update to that question:
Maybe someone can tell me what's the problem here? |
Ok I've found the solution myself. |
Sorry for not responding earlier. Yes, mapping issues are tricky. We need to improve the way we get errors from ES and somehow surface them. The selflog wont show those at the moment, you need the logs from ES itself. |
how will serilog handle if the BULK of elastic returning Error = true ? |
7 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use the Elasticsearch sink (DurableElasticsearchSink) in an IIS hosted WCF service.
Question 1: Is this a supported scenario?
Question 2: Some of my log messages aren't sent to Elasticsearch when the Message Template includes an {@MyClassValues} but in the BufferBaseFile-Bookmark file the bookmark is set to the last line. (The shipper "thinks" it has already sent the log event but I don't see it in Elasticsearch/Kibana).
An interesting thing is that some other log messages with @ destructuring operators work as expected.
The object I want to destructure is an instance of the following class:
Are there any known issues?
The text was updated successfully, but these errors were encountered: