in short: ee open source centralized modular multi-threaded high-performance log management solution with multi-platform support.quick
NXLog Community Edition 2.9.1716
Click to enlargeDescription:
The NXLog Community Edition is an open source, high-performance, multi-platform log management solution. In concept NXLog is similar to syslog-ng or rsyslog, but it is not limited to unix and syslog only. It supports different platforms, log sources and formats so NXLog is ideal to implement a centralized logging system. You can centralize your Windows, Unix, Linux, BSD, Android and application logs on Windows, Unix, Linux, BSD and Android.
NXLog can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP or TLS/SSL on all supported platforms. It supports platform specific sources such as the Windows Eventlog, Linux kernel logs, Android device logs, local syslog etc. Writing and reading logs to/from databases is also supported for many database servers. The collected logs can be stored into files, databases or forwarded to a remote log server using various protocols. The old BSD Syslog and the newer IETF syslog standard (RFC 3164 and RFC 5424-5426) is fully supported by NXLog in addition to other custom formats. A key concept in NXLog is to be able to handle and preserve structured logs so there is no need to convert everything to syslog and then parse these logs again at the other side. It has powerful message filtering, log rewrite and conversion capabilities. Using a lightweight, modular and multithreaded architecture which can scale, NXLog can process hundreds of thousands of events per second.
(to see additional options, click Buy Now)Type:
Freeware File size:
Install and UninstallOS:
Win2000, WinXP, Win7 x32, Win7 x64, Windows 8, Windows 10, WinServer, WinOther, WinVista, WinVista x64System requirements:
Min. Windows 7Language:
EnglishRecent changes in this New Release:
Added a workaround for the 256 source limit in the autogenerated QueryXML in im_msvistalog. Added a workaround for a possible windows bug when im_msvistalog was giving 'EvtNext failed with error 1734: The array bounds are invalid.' Prevent loss of unprocessed data in im_file buffers upon restart...