We did have problems with stability in the past and we had one ticket that was open for a couple of months. It was due to their platform having trouble reading sources coming from different kinds of services.

There were some problems, but they already provided a solution. Adding more RAM or CPUs solved the problem. It was quite stable and less demanding than other solutions.

It has been stable, and I haven't had any issues with it.

The stability is quite good. I didn’t notice any issues with the solution. I rate the stability a seven out of ten.

LogPoint has had a few bugs, the stability could improve.

The solution is pretty stable. However you can crash the system if you did not do the math to calculate the right sizing of the hardware. LogPoint doesn't forgive any undersized storage, memory or compute power.

Its stability is good.

I rate Logpoint's stability an eight. We face disruptions while collecting insights.

In seven years of operating it, we never had hiccups.

It is very stable. It is recognized by Gartner in the Quad evaluation of SIEM tools. They are a strong player, and their product is very solid and stable.

The solution is quite stable as long as your server and the hardware is supporting it because it is a virtual kind of software solution. So the software depends on the hardware. If your hardware is supporting it, obviously the solution will be stable. Once you install it, you don't have to worry about it.

It's a stable solution.

I rate Logpoint's stability a seven out of ten. 

There are some bugs. I think the newer version will not have such issues.

There were some glitches in LogPoint, so it wasn't as stable. For example, if we exceed our EPS, or if there are data not normalized by the editor, or logs generated by assets that LogPoint doesn't normalize, those logs won't be processed.

LogPoint can't handle multiple types of logs. For example, for IAS servers that generate various kinds of logs, such as system and security logs, at some point, LogPoint still needs to manage and understand the different logs. Sometimes, the solution discards the logs. This is why we moved to LogRhytm.

This is a stable solution. 

I rate the stability a nine out of ten.

Yes. As the product is fairly new, they do have some problems with stability.

The syslog_collector service needs some work.

The ODBC_Fetcher needs a lot of work and they do have other problems.

The solution is stable.