System Monitor Installation Guide
System Requirements for System Monitors
LogRhythm System Monitor Agents for Windows require the Microsoft .NET Framework 4.7.2.
- Before upgrading your System Monitor Agent, confirm that .NET Framework 4.7.2 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 and reboot your system. Because of the required reboot, we recommend that you perform this installation during off-peak hours.
Windows hosts running System Monitors prior to version 7.2.x may not have .NET Framework 4.7.2 installed. If your Windows host does not have .NET Framework 4.7.2 installed, we do not recommend using the System Monitor Package Manager automatic update option. Since installing .NET Framework 4.7.2 requires a system reboot, the automatic update process will be disrupted and the Package Manager will not complete the installation process.
Processor
4 vCPU
RAM
1 GB or more (minimal), 2 GB or more (optimal)
Disk Space
- 40 MB for System Monitor installation only
- 32-bit: 4.5 GB if .NET 4.7.2 needs to be installed
- 64-bit: 4.5 GB if .NET 4.7.2 needs to be installed
- At least 5 GB for log data storage
Microsoft .NET Framework
LogRhythm System Monitor Agents for Windows require the Microsoft .NET Framework 4.7.2.
Licenses
The LogRhythm SIEM provides three types of System Monitor Agent licenses: System Monitor Lite, System Monitor Pro, and System Monitor Collector. For more information, see System Monitor Functionality by License: Lite, Pro, and Collector.
Operating Systems, System Monitor Lite and Pro Features, and Agent Compatibility and Functionality Matrix
For more information about supported operating systems, System Monitor compatibility, and different System Monitor features, see the LogRhythm System Monitor Compatibility and Functionality Guide.
Troubleshooting
If you experience trouble with your Agents communicating with your deployment, check the Networking and Communication and Realtime Antivirus Exclusions pages of this guide to ensure your deployment is configured correctly.