What is our primary use case?
We work with and resell all of the SolarWinds products, and SolarWinds LEM is one of the solutions that I have experience with.
This solution is used in conjunction with others to find the root cause of problems when a user is not able to access an application.
What is most valuable?
This tool is simple to use.
The reporting and alerting capabilities are really nice.
The Heat Map is a very good feature that is related to Wi-Fi and helps to monitor access points.
What needs improvement?
It takes a long time to perform a root cause analysis.
I would like to have a more customizable dashboard.
For how long have I used the solution?
I have been working with SolarWinds LEM for four years.
What do I think about the stability of the solution?
We have had no issues with stability.
What do I think about the scalability of the solution?
This is a scalable solution. We have deployed it both in Windows and Linux environments.
How are customer service and technical support?
I have contacted SolarWinds technical support six or seven times and I think that the support is very good. The only problem is that when the system goes down, the diagnostics might take a long time.
For example, in a large environment, we had a situation where the application was down for one or two days. Normally, at most, it will take three or four hours for a large environment. In a small environment, the time that it will be unavailable due to diagnostics is about an hour and a half.
How was the initial setup?
The initial setup is totally straightforward. It takes a maximum of two hours to deploy.
What other advice do I have?
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?