![\"Event](\"\/blog\/images\/event-viewer.png\" "\\"Event")
<\/a><\/div>\n\nThe left hand side shows a tree grouping the various logs captured on your machine. The events from Windows Services (and other applications running on your PC) are filed under \nMessages from your windows service will have the display name of the service in the Source column<\/b>.\n<\/p>\n \nThe Event Viewer shows over 10 pieces of information associated with each event, including:<\/p>\n \nEach event is classified into one of three categories:<\/p>\n \n \n \nAs mentioned before, an event written by a Windows Service will contain the service’s display name as the Source.\n<\/p>\n<\/li>\n The full description shown prominently in the lower pane will (hopefully) provide the relevant details of the event.\n<\/p>\n<\/li>\n<\/ul>\n \nFor example, this information event is from the Interactive Services detection service<\/a> (“UI0Detect”) reporting that Notepad is showing itself in Session 0:\n<\/p>\n <\/a><\/p>\n \nWhile the Application log keeps track of events from a running service, the \nBoth AlwaysUp and Service Protector write messages to the Application section of the event logs ( \nFor AlwaysUp, events from your application named “My Application” will be logged with Source set to My Application (managed by AlwaysUpService)<\/b>. The Event Log Messages Page<\/a> lists and explains the events reported.\n<\/p>\n \nFor Service Protector, events related to your service named “MyService” will have a Source of ServiceProtector: MyService<\/b>.\n<\/p>\n \nAnd for both applications, events related to the starting and stopping of the underlying services themselves appear in the ![\"Event](\"\/blog\/images\/event-viewer-application-log.png\" "\\"Event")
<\/a><\/div>\n
\n![\"\"](\"https:\/\/cdn.coretechnologies.com\/images\/top.jpg\" "\\"Go")
<\/a><\/div>\n<\/div>\nImportant Components of an Event<\/h2>\n
\n
![\"\"\/](\"\/blog\/images\/event-viewer-information-icon.png\" "\\"\\""){kind=icon}
Information<\/b>: An informative yet unimportant event. You will probably see a lot of these, and they can be safely ignored unless you are digging into a specific issue from an application or service.\n<\/p>\n![\"\"\/](\"\/blog\/images\/event-viewer-warning-icon.png\" "\\"\\""){kind=icon}
Warning<\/b>: A moderately important event. These don’t necessarily signify a failure, and your software will probably limp along, but they should be reviewed regularly to see if anything mentioned can be resolved.\n<\/p>\n![\"\"\/](\"\/blog\/images\/event-viewer-error-icon.png\" "\\"\\""){kind=icon}
Error<\/b>: Indicates a critical problem or failure that may deserve your immediate attention!\n<\/p>\n<\/p>\n<\/li>\n![\"Interactive](\"\/blog\/images\/event-viewer-interactive-services-detection-event.png\" "\\"Interactive")
<\/a><\/div>\n
\n<\/a><\/div>\n<\/div>\nViewing Events about<\/i> Windows Services<\/h2>\n
![\"Event](\"\/blog\/images\/event-viewer-system-event.png\" "\\"Event")
<\/a><\/div>\n
\n<\/a><\/div>\n<\/div>\nViewing Events from AlwaysUp and Service Protector<\/h2>\n