|System Monitor (SysMon)
LogRhythm 7.12.0 GA
LogRhythm 7.11.0 GA
Microsoft .NET Framework 4.7.2 or higher
LogRhythm System Monitor Agents for Windows require the Microsoft .NET Framework 4.7.2 or higher.
- Before upgrading your System Monitor Agent, confirm that .NET Framework 4.7.2 or higher is installed.
- For information on determining which .NET version is installed, see https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed.
- If necessary, install .NET Framework 4.7.2 or higher and reboot your system. Because of the required reboot, we recommend that you perform this installation during off-peak hours.
- Linux System Monitor Agents are now completely supported on Oracle 8 and 9.
No new improvements in this release.
LogRhythm has deprecated Check Point collection via OPSEC LEA in favor of the newer Check Point Log Exporter. Support for OPSEC LEA was removed starting with LogRhythm System Monitor Collector version 126.96.36.19904 and results in an error in the scsm.log file if this collection method is used. Customers who need to use OPSEC LEA for collection should not upgrade agents past System Monitor 188.8.131.5202 release. For information on how to configure Check Point Log exporter, see Syslog - Check Point Log Exporter device configuration guide.
Found in Version
|The Linux Agent no longer fails to start in certain situations after booting on Red Hat Enterprise.
|New log sources no longer fail to capture logs in certain situations.
|Windows agents no longer stop sending beats/logs after a Mediator reconnection.
|Installing System Monitor on AIX no longer results in an incorrect build number displaying.
|AIX builds of System Monitor no longer produce errors in the scsm.log file when File Integrity Monitoring (FIM) is enabled.
|Linux Agents no longer produce unusual error messages in the system log file after an upgrade.
|System Monitor agents no longer send invalid values to LogRhythm Axon, which had resulted in invalid log sources.