Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > How reservations work on LEM

How reservations work on LEM

Table of contents

Updated January 3, 2017


This article provides a simplified explanation of how reservations work on LEM.


All LEM versions


In the LEM Quick Start Guide (pages 18-21), there is a breakdown of what the LEM must have setup by default in order to work. 


Note: The reservation values in the above document are estimates. Though a system may work given default reservations, there are many other factors that could come into play based on the hypervisor's hardware and the network environment that the LEM has been set up in. vSphere or Hyper-V are the only supported Hypervisors at this time. Any estimation on this page for sizing or for configuring settings that are being given to the LEM Virtual Machine will not constitute a baseline, but is an estimation based on our default reservations mentioned in the Quickstart Guide. The hardware in your particular environment can be different than our test scenarios, and it is not possible for us to know whether or not a system will absolutely work without being able to test that particular set of hardware devices. Please take this into consideration as you review the following information.


For example, if a Hypervisor has low IOPS (lower than 100 MB/s), it may not be adequate for the LEM to work properly, given that the LEM may be receiving millions or tens of millions of events from both the agents and the syslog.


Setting up the LEM with under 100 MB/s IOPS, would ensure that the LEM will have issues operating as the numbers increase, especially if it is sharing resources (Memory, CPU, IOPS, etc...) with other Virtual Machines.


Reference articles for IOPS from VMWare


Note: Do not deploy the LEM on consumer hardware such as a laptop or desktop computer. Deploying the LEM on a laptop or desktop computer (even though these devices may have the necessary numbers of processors and excellent memory for consumer machine), the hardware is just not designed to handle resource usage in the same way that server hardware would be, and deploying the LEM in this kind of environment you can be sure that at some point the type of processor, the speed and size of memory, the motherboard hardware, and the network interface would come into play as the numbers increase.


Does SolarWinds recommend particular hardware for LEM? No, we do not, and have not since we moved from the hardware device (SIM) to the virtual machine (LEM). Hardware recommendations are something that the specialists on your team would produce.


Given that the LEM is different from any other device as a secured/hardened appliance using Java, you should set it up in an environment where it can handle the existing traffic as well as have the option to increase reservations based on that event load.


Stable environments change over time and resource options increase based on the incoming event load. It is important to take increases in logging into account as you make decisions on where to deploy LEM or migrate the LEM to. 


Feel free to contact our technical support for further details or to help with a performance assessment on a currently deployed LEM Appliance.


For a  more technical explanation on reservations, please review the following article:

Reason for LEM Reservations


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified
10:13, 20 Feb 2017