![]() ![]() This solution provides a simple, secure, reliable, and efficient way of collecting logs from Windows Event Log. NXLog can connect directly to Windows Event Log natively, without any dependence on intermediate applications or layers. The default user interface for searching, configuring, and viewing the logs it collects is the Event Viewer. The Windows logging subsystem that collects and stores application, security, setup, system, and forwarded events is commonly referred to as Windows Event Log. It can even generate logs for various protocols by passively monitoring network traffic and capturing network packets being sent to Windows systems. NXLog is capable of collecting all types of logs from any Windows system, either natively via ETW, directly from Windows Event Log, from local log files, or remotely from Windows systems that forward events over the network. These log sources are accessed either interactively via Windows Event Log or programmatically via the Event Tracing for Windows (ETW) API. Each of these logging facilities is further subdivided into specific categories and channels such as Admin, Operational, Analytic, and Debug logs, just to name a few. Windows operating systems generate a variety of logs: the modern Applications and Services Logs as well as the legacy Windows logs for backwards compatibility with older Windows systems. ![]() Collecting all types of logs from the Windows platform ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |