Semantic logging inconsistency on EventName

Topics: Semantic Logging Application Block
Dec 15, 2013 at 3:28 AM
Edited Dec 15, 2013 at 3:38 AM
Just started with the SemanticLogging block and everything works great, except for the inconsistency in generated logs, specifically the "EventName" property with different decorations as follows;

EventName = SuperEvent1Info , expecting SuperEvent1 !
[Event(1, Level = EventLevel.Informational)]
internal void SuperEvent1(string msg)
    this.WriteEvent(1, msg);
EventName = Task1Info , expecting SuperEvent2 !
[Event(2, Level = EventLevel.Informational, Task = Tasks.Task1)]
internal void SuperEvent2(string msg)
    this.WriteEvent(2, msg);
EventName = Task1Start , expecting SuperEvent3 !
[Event(3, Level = EventLevel.Informational,  Task = Tasks.Task1, Opcode=EventOpcode.Start)]
internal void SuperEvent3(string msg)
    this.WriteEvent(3, msg);
Don't know If I'm missing any configuration or this is a bug, but expecting "EventName" to just equal the EventName, not to be affected with tasks/opcodes or even pre-appended with default opcode "Info".

I have tested this with the three default formatters, Text, XML, and Json and resulting the same behavior.

Thanks for any help.
Dec 16, 2013 at 7:12 AM
This behavior seems to be by design. See for a similar question.

Perhaps create a work item at the SLAB site, to track this.

Randy Levy
Enterprise Library support engineer
Support How-to