Zabbix exploitation has dispensed with financing frequent visits of technical area through alerts, notifications and statefull map. Thus the return on investment is more than 100%
Network Monitoring Software Exploit Reviews
Showing reviews of the top ranking products in Network Monitoring Software, containing the term Exploit
SevOne Network Data Platform: Exploit
The initial setup was very straightforward. It was really more of an issue just to get the money. And then once we had the money, it was very straightforward to roll it out.
We were driven by two migrations off of legacy components. It took us less than six months to get off the first system we were exiting, and then we spent another six months getting off the subsequent system. So it was probably about a year before we got off two of our original legacy performance management tools. And most of that was really around getting the data feeds sorted out, ensuring all the devices that need to be managed were part of automatic feeds into SevOne. SevOne itself is straightforward because it's an actual appliance base and it does not require much effort required to band it up.
Our implementation strategy was to replace like for like before exploiting any extra features of SevOne. We were collecting team metrics of 20,000 boxes. Then the replacement had to do the same as a starting point in order for us to exit the old system. So it was pretty much like for like, in terms of the implementation. And we did have a mix of PaaS and VM boxes as well. So we do have a mix within our environment for the collectors.
Plixer Scrutinizer: Exploit
reviewer1249062 says in a Plixer Scrutinizer review
Network Manager at a energy/utilities company with 5,001-10,000 employees
We have tried to extract a map of data flow information, but I think we have to use a JSON query with API in order to query Scrutinizer to pull out some information in order to make some correlation with other third-party tools. We never had the opportunity to do this. It is something that would be nice to do, but it's very labor intensive.
I really would like to exploit the metadata to match it with other applications using the API, but this is not yet available. I'm not sure that we'll go that way because all the work that we have to do in order just to extract the metadata from Scrutinizer. We'll have to correlate with all the information from other systems. For that reason, I'm not sure it's going to happen. It will be very interesting though.
I would like them to improve the update process. It's so complicated now that it switched to Linux. This makes the server more stable because before we were running it on Windows. The fact that they use Linux is very good and makes it more stable. However, updates never happen in one day or on our own. So, every time we need to call Plixer to proceed with the update, and they are very efficient in that. However, if they could make it a bit easier to upgrade, e.g., a click from the web interface to update the system, this would be nice.
For updating the Scrutinizer platform, when we have the actual data, it never happens in one day. Every time we have the data, we are obliged to install a new server in order to integrate the old data, and every time it has a problem. Most of the time, we were obliged to scrap all the data because we couldn't transfer it to the new server. So, it would be very good if they could improve this part.
Concerning the NetFlow, we have encountered many issues with some routers that don't send proper tickets. All the time, we're obliged to logon to SSH and run pcap. Pcap is just the packet capture. We are obliged to enter into the Linux to run some pcap on the common line, which is not great. It would be very nice if they integrated the pcap features through the web in order to analyze them. It's very easy. Most of the tools that we're using, and that are on the market, provide this feature. It would be great if Plixer integrated the pcap functionality through the web interface without having to enter into the Linux system.
The security part could also be improved. It would be great if they could implement a better algorithm inside the Scrutinizer to detect if there were attacks. The current algorithm to check if there has been a DNS attack is very light.