Rolf Kristensen

Not like there is an army of developers sitting ready under the NLog umbrella. The current focus for the NLog-project is working towards NLog v6 - https://nlog-project.org/2024/10/01/nlog-6-0-goals.html

You can add your own [custom fields](https://github.com/farzadpanahi/NLog.GelfLayout?tab=readme-ov-file#sample-usage-with-custom-extra-fields) like this: ```xml ``` See also: https://github.com/NLog/NLog/wiki/Level-Layout-Renderer

> So I had a look at the FileTarget - when you modify one of the configuration properties, e.g. change the ArchiveFileKind, or ConcurrentWrites they seem to call ResetFileAppenders -...

NLog supports some runtime modification of the LoggingRules without loosing LogEvents. But yes when re-assigning new NLog configuration, then one can loose in LogEvents in the transition-phase (closing old /...

Alternative you could remove `[NLogConfigurationItem]` from `SentryNLogOptions`, and maybe move any convience-properties from `SentryNLogOptions` to the NLog SentryTarget directly: ```c# [Target("Sentry")] public sealed class SentryTarget : TargetWithContext { [NLogConfigurationIgnoreProperty] public...

When having released NLog v5.4 then make pull-request to update EcsLayout to use `Layout.FromString`

Closed by #5681

Pull-requests are always welcome: - Notice `master` is for NLog v5.4 (Stable) - Notice `dev` is for NLog v6.0 (High chance of conflicts)

NLog v5 no longer automatically loads NLog assemblies with wildcard (`NLog.*`). Instead one have to explicitly specify the wanted assemblies (Reverts the auto-load introduced with NLog v4). Think this removes...

Assembly preload logic was removed for NLog v6 with #5621