I went about this a bit differently, but this approach generates emails on new events that match a custom filter, with all the event details included in the email body.
1) Create a 'Custom View' in the Event Viewer with your desired filter.
2) Once you have the view, you should see a link to 'Attach Task to This Custom View...'.
I chose to use sendMail.exe from here (http://caspian.dotconf.net/menu/Software/SendEmail/) which I extracted to C:\sendmail. The reason is Microsoft's 'Send an email' action has issues with SMTP authentication and also apparently isn't even present in Server 2012.
So in my case I selected 'Start a program' while attaching the task to the Custom View. But we're going to edit it as XML so don't worry about filling it in via the GUI.
3) Export the new Task to XML, we'll be editing it later.
4) Create a 'mail-event.bat' file under C:\sendmail folder with the following 3 lines:
C:\Windows\system32\wevtutil.exe qe Application /f:text /q:"<QueryList><Query Id='0' Path='Application'><Select Path='Application'>*[System[(EventRecordID=%1)]]</Select></Query></QueryList>" > C:\sendmail\%1.log
C:\sendmail\sendEmail.exe -s <smtp_server> -f <from> -xu <user> -xp <pass> -t <to> -u "<subject>" -o message-file=c:\sendmail\%1.log
del C:\sendmail\%1.log
Obviously, replace 'smtp_server', 'from', 'user', 'pass', 'to', 'subject' with the desired values.
This will create a '$(EventRecordID).log' file under C:\sendmail with all the details for that event, mail it, and then delete it.
You can test if the batch file works by going into Event Viewer, opening an event in your Applications log, switching to Details tab, selecting 'XML View' and then look for EventRecordID. Copy that integer, and then run from the command line:
C:\sendmail> log-event.bat 53522
Of course, replacing 53522 with the value from the EventRecordID node. If you receive the email, go to your happy place.
NOTE WELL: You might have noticed the string 'Application' shows up a couple times in the command line for wevtutil.exe -- that's because I couldn't seem to get it to work by pointing it directly at the Custom View, and my Custom View happened to be a sub-set of events that are all inside the Application log. You might have to adjust that to make it work in your case if your trying to mail events from the System log, for example.
5) Edit the XML you exported, we're going to make two changes:
First, add the following 'ValueQueries' node into the XML under the 'EventTrigger' node:
<EventTrigger>
<Enabled>true</Enabled>
<Subscription>...snip...</Subscription>
<ValueQueries>
<Value name="EventRecordID">Event/System/EventRecordID</Value>
</ValueQueries>
</EventTrigger>
NOTE: In the above, I snipped the 'Subscription' info which will have been filled in based on the Custom View you created. Don't copy my 'Subscription' into your XML!
Second, replace the Actions node with the following:
<Actions Context="Author">
<Exec>
<Command>C:\sendmail\mail_event.bat</Command>
<Arguments>$(EventRecordID)</Arguments>
</Exec>
</Actions>
Now, cause a new event to appear in your Custom View, and you should automatically get the email notification! Woohoo!
Microsoft purposely prevents you from doing this. The whole concept of the Event Viewer is to present to you certain events that may require your attention. If one could go in and delete any random event, then the system could - in a sense - be compromised without you knowing, therefore making it unsafe.
If you have an error event logged, find out what is causing the problem and fix it. You don't want to patch a hole in a dam by sticking a wad of gum in the hole.
If something is logging informational or caution events too often, then many times the event log source (either Microsoft or a third-party) has some setting that indicates how often or to what level of logging is configured for the application. That is where you go to minimize the logging, not by doing surgery on the event log.
Best Answer
You need to add the source in the code of your web application, using:
Source