User Requests
The following is one of the user requests that was received.
1) being able to forward a log item to a DB, possibly in asyc mode (e.g. MSMQ, BITS) and/or to MOM/SMS for analysis and proactive maintainance (e.g. push out a FIX with SMS)
2) group events into 1 items instead of having hundreds of same items
3) please do the logs in a XML (parsable) format
4) ability to redirect/map logs to a network share
5) Larger default sizes
6) Automatic rollover (daily/weekly/x items)logs - old logs to be stored on disk
Here is the reply
1) It will be possible to subscribe to a log using a filter. The subscriber could then forward the events.
2) Right now there is no plan to support Event aggregation as part of service natively but this can easily be done by enterprise products which are written on top of this infrastructure.
3) The new system is based on xml. The internal format isn’t xml text, but getting an xml representation of the log will be quite easy through rendering. A utility will ship that will take an xpath expression and create an xml text file
4) The issue with that is that the service will not generally have access to network share. It will be possible to create or read backup on the network, but not to have live logs there since that requires the service to have access without an active client. Two things which might help here. The firt one is that new Eventlog does provide the way to change the local location for the log. Secondly, one can use Event forwarding to forward it to other machines.
5) Done
6) We do have the capability to create a backup and clear the log once it hits a certain size. We don’t base the backup on time in eventlog service. Alternatively, one can schedule a task (based on new Task Scheduler) to run a commandline at a certain time.
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
