verbose, information, warning, error, and critical error, for each message being written is an important component in providing logs that are easy to filter. Also, selecting the appropriate log level, i.e. The best way to address undesired log entries is to handle the events that generate them appropriately within the application. This is purposely designed that way for a number of very good reasons. There is no supported way to delete individual log entries from Windows Event Logs. I know that this is a late post to a dead thread but hopefully it helps someone else who is Googling this more than posts of "" -) Now when you wish to look at your event log, use your custom view and only the information you are truly concerned with will be displayed. If you want to find actual problems and you have specific event ID's that you don't care to weed through, create a custom view with the following steps: there is nothing to "fix" as it is not a problem. It is an error of no concern in most cases. It simply means that you have a printer mapped with a driver that is not available on the server to which you are connected. One of the errors he is talking about is (I think) event ID 1111. Good or bad, this is just a fact of life. When too many "errors" are reported and most of them are low priority or of no concern at all, administrators tend to ignore ALL errors. The number one problem with logging, error reporting, and alerting is white noise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |