-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About log.level JSON format resolve failed #8470
Comments
Hi @haoma2514, how do you ingest the logs? The client does not modify the ingested documents/logs in any way. You always get exactly what's stored. This means you have to address this issue on whatever place you use to ingest the logs. |
FYI: The The raw document however is not modified. If you need the property expanded in your .NET application, you have to make sure it's stored in the correct format in the first place (or you implement a custom JsonConverter for your log type and use that for deserialization). |
Thank you for your reply. The log is written through Elastic.Extensions.Logging, for example: builder.logging.addelasticsearch (); I don't have a custom mapping relationship or an index template. Could it be Elastic.Extensions.Logging? In addition, I would like to ask, where can I quickly learn the client usage of V8 version? |
Yes, in this case it seems to be the way how The official documentation for the client is here: https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/introduction.html. Improving it with more examples is something that's being worked on. Please let me know, if you have more questions. |
This issue is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue was closed because it has been stalled for 2 days with no activity. |
Elastic.Clients.Elasticsearch version:8.17.1
Elasticsearch version:8.17.2
.NET runtime version:8.0
Operating system version:Windows 10 21H2
Description of the problem including expected versus actual behavior:
A clear and concise description of what the bug is.
Steps to reproduce:
1.
3.Log mapping to an object contains the Level attribute, but it becomes the "Log.Level" attribute after being obtained by the client.
Expected behavior
"level" is a property of the log object
The text was updated successfully, but these errors were encountered: