[LOG4NET-674] Document how to add custom levels to log4net repository

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.8
• Component/s: Documentation
• Assignee: Unassigned
• Reporter: jeff
• Created: 09/Sep/21 00:04
• Updated: 09/Sep/21 00:04

Description

It seem like in most cases just creating a level instance and using it will add it to the hierarchy but there appears to be an exception when using the eventlogappender level mapping configuration option. 

When configuring the eventlogappender level mapping, it was difficult to map custom log4net levels to a windows level.  I was unable to find documentation on how to load the custom log4net levels in to the map in the appender. The final solution that seemed to work was adding level to the configuration file, which I found on some other thread related to filtering. This allowed me to map my custom log4net audit levels to an equivalent event log level/keyword. 

 

Maybe some documentation on how to programmatically and via configuration add custom levels to log4net. A note on the eventlogappender level mapping about how to map custom events would be useful. 

 

via code...

public static class CustomLog4NetLevels

{ private static readonly Level successAudit = new Level(105000, "SuccessAudit"); private static readonly Level failureAudit = new Level(106000, "FailureAudit"); /// <summary> /// Audit Sucess Level /// </summary> public static Level SuccessAudit \{ get => successAudit;}

/// <summary>
/// Audit Failure Level
/// </summary>
public static Level FailureAudit { get => failureAudit;}
}

LogManager.GetRepository().LevelMap.Add(CustomLog4NetLevels.SuccessAudit);
LogManager.GetRepository().LevelMap.Add(CustomLog4NetLevels.FailureAudit);

 

or via config

<log4net>
<level>
<name value="SuccessAudit" />
<value value="105000" />
</level>
<level>
<name value="FailureAudit" />
<value value="106000" />
</level>....