Netsurion is stable. I have not encountered any issues.

At times, the agent may consume a lot of resources, but that typically happens when the agent is running on some assets that are near the end of life. 

Netsurion is highly stable. I haven't had any issues. However, the agents on the endpoints seem to fail quite a bit, requiring manual involvement from the local administrators. I would like to see their product be much more ad hoc and update automatically. I'd like to know if it has errors or issues to support that. Otherwise, local people need to uninstall and reinstall, and it's very time-consuming to maintain the installed product. This should be automatic. We shouldn't have to deal with that on a routine basis.

It has been very stable. We have had no major problems with it. We might need to put in one or two calls because of an issue logging into the software. I think we had a problem one time with a disk partition filling up, which hauls a lot of data in and out. So, that is something where you just have to be aware of it, but they have always been very responsive. There have been a few times when we might have had to go in and re-enable their remote access. They always notify us when they are going to be on that server, so we are able to tell when that outside third-party is accessing the server. So, stability has been good.

The stability has been very good. 

The only time we might have had downtime was based on our requirements where we were moving to new hardware. That doesn't happen much now because we're virtualized. But we tend to archive a lot of the data so we've moved that backend data store a couple of times. They'll either walk us through it, or they'll just take care of it if we don't have time for it.

In fact, later this afternoon we're doing exactly that. We're moving off of an older SAN to a newer SAN. We'll disconnect the old SAN, validate that all the data is flowing the way it should be in the searches and that the search capability against the archive database is still valid. Overall, it's really pretty simple.

I don't have any stability issues. 

The stability has been mostly okay. There have been the odd times where agents weren't able to report in. For example, there was the odd time where the software agent had issues on clients, then reported as offline or not reporting, even though it was online. That was a bit annoying at times. The hosted on-premise hardware that we were using was having issues. This is the only time that I will call "Fault" to the hosted SOC. The performance of it was horrendous, but we weren't using it. It was being all done through the SOC and the performance was horrendous. If it was that bad, why wouldn't they have perhaps said something? Why were they struggling with delivering reports or fighting with the server on our behalf? If it was struggling that bad, why wouldn't they have said, "Hey, this machine has problems. We need to do something about it"? 

We didn't know or do anything about it until we needed to check on something, then realized that the performance on it was horrendous and there were severe hardware problems with the server. Then, that spiraled into actually replacing it and the SOC team didn't mention anything. So, that was a bit of a frustration. If they were struggling with something that bad, then why didn't they say something?

I've never known Netsurion to go down.

The stability has been really great.

On the older version — and this might have even been with version 7 — we had one or two instances where we had a problem logging in with our Active Directory account. We never really got a lot of details, but I can tell you that in less than 15 minutes they had it corrected. They have VPN capability as part of the managed services to be able to get in anytime they want. That VPN capability has two-factor authentication on it. We opened a ticket with them, told them what was going on, and they came in via VPN and corrected the situation.

We did have this issue twice, about nine months apart. But we have not had that problem in version 8 or 9. I don't know if it was something within the server configuration or something else. Other than that, we've never had any stability problems. 

The query timeouts, again, were just due to the sheer volume of data that we were trying to extract out of the thing. It was something we were able to work around. We could do a couple of extractions and bring them back together. It wasn't anything that was a big pain for us. It was a little bit of a learning curve and understanding.

In the early days of it we were really trying to get everything. But they were really great and said, "Well, that's great, but after you get everything, then you've got to pare it down anyway. So why don't you just build your query in a way that is smart enough to get only what you really want to begin with. So when you do get your extract, it's ready to work on." That was part of a learning curve for us and their suggestion really helped out a lot.

It has been extremely stable. Very rarely do we even realize that it's still running, and that's good.

It's okay for what it does. They're trying to add more different capabilities. One thing that I will be interested in, when and if we upgrade to a new version, would be the different types of alerts offered. They do have some different type of prebuilt alerts. The big thing is it's hard to know what things EventTracker may not be alerting on. They do have the behavior correlation part, but when I looked at that, it was using Elasticsearch. Since our Elasticsearch wasn't working that well, this was sort of problematic as there are a bunch of different false positives and stuff.

We sort of knew there would be issues when we did the upgrade because of Elasticsearch and our spinning disks. The searching isn't as easy as it could be, as far as the three different search things that you can do. 

This is same with the different dashboards, as related to Elasticsearch. If we were to implement a brand new version and didn't have the hardware already, we would say, "Okay, we'll wait until we get the SSDs." But, we sort of earmarked a server. The hardware was on the old EventTracker. So, when we did the upgrade, we knew it was going to be an issue, but we didn't know how big of an issue it was going to be.

I have not seen anything that has been detrimental in using the services. However, using the tool tends to be slow sometimes.

It is as stable as a rock. I have not heard of a single outage on it.

The only stability issue we've run across would be the log forwarding off of the devices occasionally hanging up. I don't know if that's the EventTracker agent or the server itself, because there are a lot of applications running on those servers. But the console itself, I don't think it's ever been down, other than his patch which we just experienced.

Other than updates, there has been no downtime. It is very stable.

Stability has been okay. We've only had one instance where specific endpoints were not reporting in. During the discovery, we found that devices were pointed to the wrong collector on the Netsurion side, and they fixed that.

It is very stable.

It has been very stable for me. I can't say that I have ever known it to be down in the last four years unless we were rebooting it ourselves to do maintenance, like caching on the server.

Version 9 was a tremendous upgrade for the dashboard. The performance of the new version with the Elasticsearch edition is a real improvement. Previously, running reports would take a long time, and now reports are very easy to slice and dice, then look through the data and dashboards. The dashboards are very helpful if I want to add a new widget. I can email the control center, then they will just add it to my dashboard for me.

It's really stable. It's pretty low-maintenance, once you get it set up, as long as the server that it's hosted on is up. We haven't really had any issues with a system problem with EventTracker since we implemented it.

It's very stable. We put it in place and have ignored it except, for pulling the reports.

It is very stable. The product has been very smooth to work with recently. I am extremely happy with the way that it is right now.

We have had issues with it in the older versions (7.2). Because of our number of events that we generate, it used to stall and take a long time to do searches. Once we upgraded to 8.2, it pretty much resolved those issues. It was around 2015 when we upgraded.