Windows Event Monitoring & Forwarding
Grossrinderfeld, 2012-08-29 Adiscon is proud to announce the 12.2 release of EventReporter. This release includes a little new feature. A new option “Clear logfile instead of deleting (File will be reused)” was added into the File Logging Action. For more details read the 12.2a version history and the 12.2b version history
1. Overview This article gives an overview of MonitorWare Line of Products and provides a guideline to select the right product. This article discusses EventReporter, MonitorWare Agent, WinSyslog, MonitorWare Console, Monilog MonitorWare Agent, WinSyslog and EventReporter work on common concepts but target different needs. They also come in different editions and versions. Click on MonitorWare […]
Grossrinderfeld, 2012-03-05 Adiscon is proud to announce the 12.1 release of EventReporter. This release includes performance enhancements and bugfixes. With this release, we offer support for the “CEE enhanced Syslog Format“, a format that intends to ease event processing. A multi-vendor community including Red Hat, MITRE, Balabit and Adiscon will build a better logging infrastructure […]
Release Date: 2012-03-05 Build-IDs: Service 12.1.351, Client 12.1.0.414 Features EventLog Monitor V2: Added support for resolving SID’s (Security Identifier) in. The Option is automatically enabled for the Security Channel, for all others the default is off. Added support for named properties if available. Forward Syslog Action: Added support for new “CEE enhanced Syslog Format” […]
Release Date: 2011-05-16 Build-IDs: Service 12.0.347, Client 12.0.0.401 Bugfixes Fixed a memory leak in all TCP releated actions that could occur if the TCP session timeout was set to a low value. Fixed a problem with the session timeout calculation for TCP releated actions. If the value was set above 3 minutes, the calculation […]
Release Date: 2011-05-03 Build-IDs: Service 12.0.346, Client 12.0.0.400 Features Added support for IPv6: Support for IPv6 has been added into all network related facilities of the engine. All network related actions will automatically detect IPv6 and IPv4 target addresses if configured. You can also use DNS resolution to resolve valid IPv6 addresses. Network related […]
You can come across this specific error, by reviewing your EventLog data. The EventLog Monitor writes an entry to the EventLog and then retries. If debug is activated, a entry will be created there, too, looking like this: “2212 | 1175784330 | Error | Error FormatMessage return 0, GetLastError = ‘317’” The reason for this […]
Created 2007-04-10 by Rainer Gerhards. Starting with EventReporter 8.3 and MonitorWare Agent 4.3 two different event log monitor services are provided. They are called “Event Log Monitor” (V1) and “Event Log Monitor V2”. In short, the V2 version is recommended for Windows Vista (and above, e.g. Longhorn Server) while the other version is for previous […]
SystemID It is a user-configurable numerical value that has been added for grouping a group of systems and improves filtering. It is just like a numerical code to which you can assign a value and query it afterwards. CustomerID It is similar to SystemID. It depends on user that how he uses these. Let us […]
The general options of each product (EventReporter, MonitorWare Agent and WinSyslog) contain a setting for the “Default Timevalues”. This setting can be set to Localtime and UTC (Universal Coordinated Time) which is default. If you switch this setting to Localtime, you may wounder why output timevalues still are in UTC. Internally we need to calculate […]