SolarWinds Security Event Manager Reviews

We were suffering from a lack of visibility into our logs, so we implemented SolarWinds LEM. After building a few rules and alerts, we were notified when events happened before our end users notified us. Many times we were able to fix an issue before a call to the helpdesk was made.

• Alerting
• Searching

The solution was a little slow when running some larger queries. After upgrading our SAN many of the problems disappeared.

Tech support was always on top of things. I usually got a response within a couple hours of opening a ticket and once on the phone, they took time to answer my questions.

We needed a product but didn’t have one. We found it when it was still Trigeo, and followed it to SolarWinds.

The initial setup was very easy to start getting logs to the solution. It took some time to understand what data to get and what was important.

We did the implementation. My advice, understand what you want in the system and after letting it collect some data, swing back and make sure you have everything setup that you need. Give it some time, and learn it to get the most use out of it.

It’s a great product, but like other SIEM software solutions, you only get out what you put into it.

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.

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.

It takes a long time to perform a root cause analysis.

I would like to have a more customizable dashboard.

I have been working with SolarWinds LEM for four years.

We have had no issues with stability.

This is a scalable solution. We have deployed it both in Windows and Linux environments.

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.

The initial setup is totally straightforward. It takes a maximum of two hours to deploy.

I would rate this solution an eight out of ten.