In the first post of this series I've manage to find the correct eventId for each Web Event type, and by this time the major problem has been solved, but I cannot yet write a correct entry into the EventLog.
I still have to decided the best severity type and category to apply.
If you look at entries in the EventLog generated by the default EventLogWebEventProvider you will find that they are marked mainly as Information and a few of them are also marked as Warning but no one is ever marked as Error.
Since I'm making my own provider I will take this chance to map the EventLog entry severity type according to the source Web Event.[more]
Naturally, you can decided to map the Web Events exactly has the default EventLogWebEventProvider does.
Finally all I need is to do is set the correct category for the Web Events.
Although all Web Events belong to the same category 'Web Events', the problem is how to make the correct text appear.
The value shown in the category property is a resource string and to select the correct category value is necessary to set the exact resourcekey.
That is not so hard to do, I could have made my own resource assembly with only one resource, but I have a better way ... I will use the same resource assembly that ASP.NET use.
To figure out which assembly to use I simply used regedit.exe to look at "HK_LM\System\CurrentControlSet\Services\EventLog\Application\ASP.NET 2.0.50727.0"
What I look for are the settings used by the "ASP.NET 2.0.50727.0" EventLog source which is the source used to write the Web Events EventLog entries.
The settings I will use are the CategoryCount and CategoryMessageFile keys because they are the ones that instruct which category assembly to load.
Please note that the CategoryMessageFile may change according to operating system and ASP.NET version.
Finally, I need to know the exact resourcekey of the "Web Event" string, and since there simply 5 resources in assembly it took no time to get the following table:
Category Resource Key
Now I simply need to configure my EventLog source to use those same settings.
As I said in part 1, you can create an EventLog source using the EventLog.CreateEventSource method, but for setting the CategoryCount and CategoryMessageFile values you must use this specific overload EventLog.CreateEventSource(EventSourceCreationData sourceData).
That's it ... I've got everything I need and the final result look like this:
It looks similar to the usual but if you look closer you will find the differences.
What you need to keep in mind is that:
- the EventId and Category values are keep unchanged;
- the entry Type respects the Web Event type as opposing to the EventLogWebEventProvider given by ASP.NET that only uses Information and Warning;
- the EventLog source can be one of my choise (not the usual "ASP.NET x.xxx") and can change by application;
- you can choose either to use the existing EventLogs or to create a brand new one for your application(s) .
As a final note remember that with this provider you can now organize your application EventLog entries into specific EventLogs, and you may also filter them by application Source.
Download the code here.