System.Diagnostics - Eventsource with empty message

Question

I'm using System.Diagnostics to get some messages using EventSource, to trace them as a log. It appears that some informations are missing, as for example the EventMessage and the Message (they are empty), while the EventId and the Level are correctly set. The WriteEvent method is correct (The number and types of arguments passed to every event method exactly match what is passed to WriteEvent()). In particular, I am using WAD on a ServiceFabric Cluster to collect traces on an Azure Table Storage. Any idea?

Thanks!

any update? Have you tried to record the events via Perfview into an ETL? — magicandre1981, Aug 28 '16 at 07:01

score 0 · Answer 1 · answered Jan 16 '16 at 16:02

0

The parameters of the Event must match to the parameters of the method which you call. Eventsource builds the manifest based on the parameters of the method.

Event methods must match exactly the types of the WriteEvent overload it calls, in particular you should avoid implicit scalar conversions; they are dangerous because the manifest is generated based on the signature of the ETW event method, but the values passed to ETW are based on the signature of the WriteEvent overload.

answered Jan 16 '16 at 16:02

magicandre1981

27,895
5
86
127

I do it, I am passing the exactly number of parameters with the same type. – user2867270 Jan 18 '16 at 08:59
Try the NuGet version of Eventsource – magicandre1981 Jan 18 '16 at 17:22
I am trying to, but it seems not all the messages are handled. Can be that WAD or EventSource send only events classified with certain keywords or certain leve? – user2867270 Jan 19 '16 at 11:07
I only collect the data via WPR.exe into a ETL file, so I have no idea if other collecting tools have issues. – magicandre1981 Jan 19 '16 at 16:06
It seems that it depends on which machines the process is running: if I collect data on 5 machines by the same application partitioned into different machines, only after a restart it seems to works. – user2867270 Jan 20 '16 at 11:01
try to capture the events via Perfview and look if this includes all data: `PerfView /providers=*MyEventSource run MyApp.exe` – magicandre1981 Jan 20 '16 at 16:18
have you tried perfview to log the events into an ETL file? Can you see all data here? – magicandre1981 Jan 24 '16 at 15:22

score 0 · Answer 2 · answered May 11 '18 at 13:06

I have had this problem ever since we upgraded to any version of the .NET Framework greater than 4.5.2. I finally figured out my problem and hopefully, this will help you too. I know this is an old post, but maybe it will help someone else as well.

It seems Event Tracing for Windows (ETW) handles errors and the only indication you get is what you're seeing where the logged message is null. I am using a custom formatter derived from IEventTextFormatter. (the EventData.FormattedMessage is null). Setting a breakpoint in this method showed the EventData.FormattedMessage was null. I also noticed the following messages in the Output/debug window in Visual Studio:

The parameters to the Event method do not match the parameters to the WriteEvent method. This may cause the event to be displayed incorrectly.
EventSourceException while processing event "WriteLogDefault": System.IndexOutOfRangeException:Index was outside the bounds of the array.
A first chance exception of type 'System.NullReferenceException' occurred in NEAM.App.ProfileDataMart.BL.dll

I traced my problem to the following method:

[Event(1, Message = "{2}", Level = EventLevel.Informational, Keywords = Keywords.Informational)]
private void WriteLogDefault(int p_EventId, string p_AssemblyName, int p_Key, string p_Message)
{
    WriteEvent(p_EventId, p_AssemblyName, p_Key, p_Message);
}

Based on the remarks in the docs on MSDN, the call to WriteEvent should include the EventId followed by all the arguments passed to your method. Evidently, the above code did not throw any exceptions in .NET Framework 4.5.2 or earlier.

When you implement a method that is identified as an ETW event in an EventSource-derived class. You must call the base class WriteEvent method passing the EventId and the same arguments as the implemented method.

My code now looks like this and works as expected. Good luck!

    [Event(1, Message = "{2}", Level = EventLevel.Informational, Keywords = Keywords.Informational)]
    public void WriteLogDefault(string p_AssemblyName, int p_Key, string p_Message)
    {
        WriteEvent(1, p_AssemblyName, p_Key, p_Message);
    }

System.Diagnostics - Eventsource with empty message

2 Answers2