Elasticsearch.Net.UnexpectedElasticsearchClientException: Failed to serialize anonymous type when writting to NLog about elasticsearch-net HOT 3 CLOSED

It seems like you are using a 3rd party package NLog.Targets.ElasticSearch. If you can give me a code which is able to reproduce the problem without using that package, I'm happy to investigate further.

Otherwise, please first ask the author of NLog.Targets.ElasticSearch to check the bug 🙂

from elasticsearch-net.

Hi,

This is a duplicate of this issue on Nlog.targets markmcdowell/NLog.Targets.ElasticSearch#182

For this issue, when setting NLog to log to file target only, I have no problems. Only when trying to log onto elastic cluster v7.10.2, on NET8.0.
Here is a link to a sample repo, which has the same problem, when we take a look at the internallog file which is generated after running the webapi project.
It only needs a running elastic cluster to see the problem
https://github.com/fsimonovski/NLog-ElasticSearch-Net8
Thanks for the help.

from elasticsearch-net.

Hi @fsimonovski,

it seems like a workaround was already suggested to you here.

NEST 7.13.2 is very old and I unfortunately can't spend any time digging into that. You could try to upgrade to NEST 7.17.x or even better to the new 8.x client. Please as well note that NEST is deprecated and will reach end of life at the end of the year.

The problem seems to be the changed type Microsoft.AspNetCore.Routing.RouteEndpoint which is not related to NEST. Probably this type got changed as well in the NET8 packages of AspNetCore and causes the issues. My advice is to never serialize any external complex types over which you don't have control. Creating a custom DTO object and just assigning the primitive properties to it in which you are interested to log, is most of the time a way more robust solution.

from elasticsearch-net.