Root > Advanced topics > System logging setup > System Log

System Log

Previous pageReturn to chapter overviewNext page   

Many applications record errors and events in proprietary error logs, each with their own format and user interface. Data from different applications can't easily be merged into one complete report, requiring system administrators or support representatives to check a variety of sources to diagnose problems.


Event logging provides a standard, centralized way for applications (and the operating system) to record important software and hardware events. The event logging service records events from various sources and stores them in a single collection called an event log. The Event Viewer enables you to view logs; the programming interface also enables you to examine logs.



Event Viewer in Windows Vista+



Event Viewer in Windows XP


Applications can use the Event Logging API to report and view events. While any application can log events with Event Logging API, Win32 service applications use Event Logging most commonly.


Note: while it is recommended to use System Log for Win32 service applications, it is not strictly required. Win32 service applications can use typical EurekaLog bug report files instead of System Log.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2018-06-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: