Rolf Kristensen

Can only repeat that you can use work around by setting MaxRecursionLimit="1" The bug is in NEST / Elastic-Client, and this is not support forum for NEST / Elastic-Client

NLog.Targets.MauiLog calls the official API provided by Apple / Microsoft / Xamarin / MAUI: https://github.com/NLog/NLog.Targets.MauiLog/blob/94af31cb1a49be02b2f9d163ec3096bb27547d3f/src/NLog.Targets.MauiLog/AppleOSLogTarget.cs#L58-L77 If there is something that can be improved either in implementation or in documentation, then...

I was thinking that one would use the native LogViewer on the actual device. - Android would use [LogCat](https://developer.android.com/studio/debug/am-logcat) - iOS would use [OSLog Viewer](https://medium.com/@ajvanderlee/oslog-and-unified-logging-as-recommended-by-apple-47fad0d73282) - Debugging in Visual Studio...

Closing due to inactivity. If you find something that can be improved, then pull-request are most wellcome.

master-branch has been updated. Just awaiting a release-build and publish to nuget. @markmcdowell Anything missing for publishing a new release to nuget?

Believe the repo-owner @markmcdowell controls the nuget-key

Notice that ElasticSearch have now released their own official NLog Target for ElasticSearch: - https://www.nuget.org/packages/Elastic.NLog.Targets/#readme-body-tab - https://github.com/elastic/ecs-dotnet/tree/main/src/Elastic.NLog.Targets

@johnjaylward The [Wiki](https://github.com/markmcdowell/NLog.Targets.ElasticSearch/wiki) mentions that you can assign `opCodeCreate="true"` to enable data-streams. See also #132

No idea. Maybe look in the ElasticSearch-manual or ask ElasticSearch-support or use StackOverflow.com or Google how `opCode` is working.

From the [Wiki](https://github.com/markmcdowell/NLog.Targets.ElasticSearch/wiki): > When connecting to Elastic-Server 8.0 make sure to use `documentType=""` to avoid unknown parameter error.