Microsoft Security Specialist at a comms service provider with 51-200 employees
Real User
Top 10
Jun 22, 2026
The single biggest friction point I experience with ManageEngine NetFlow Analyzer comes down to database storage management and disk space explosion, as flow data records literally record every single conversation passing throughout the monitored interfaces. The volume of incoming logs is absolutely massive, so if I do not stay on top of the backend settings, the tool can easily choke the server. ManageEngine NetFlow Analyzer is absolutely a powerhouse for traffic forensics, and using it heavily day-to-day definitely highlights a few gaps where I end up thinking I wish it just did that natively, such as native built-in traffic shaping or direct remediation. If I could change one thing about ManageEngine NetFlow Analyzer, it would be transforming the tool from a purely observational platform into an actionable, active remediation tool. When I am sitting inside the ManageEngine NetFlow Analyzer dashboard and spot an internal machine maxing out one link, the tool does a flawless job of showing that I have a culprit, but that is where its job ends. To fix it, I have to break my concentration completely, leave ManageEngine NetFlow Analyzer, and pull up the SSH terminal to log in to the specific switch or the router CLI and manually apply a rate limit or drop the connection.
ManageEngine's product has some performance issues. It runs very slowly when the system is large and does not support high availability for big flow and high-level operations. The product needs improvement in supporting high availability for active-passive or active-active configurations when building for a large system. The price could be improved.
Sometimes customers are unaware about their own network. For example, we need SMTP credentials for Layer 2 switches to do automatic discovery of network devices. Sometimes the network management teams are unaware of their SMTP credentials because the teams have been shuffled since the network was deployed. Or sometimes, when we support our government and defense customers, they don't have clearance to share these credentials with us. Some of the features, such as auto discoverability, get hampered if the customer is not aware of their own network or somehow can't share privileges and credentials with our tool for them to work properly. Not in ManageEngine NetFlow Analyzer in particular, but there are other features of the OpManager suite that could afford to be updated. There is something called a CLI, command-line interface, that allows us to configure network devices such as switches. This is old technology. This product suite has CLI-based configurations, but as of last year, most network devices come with Zero Touch Provisioning (ZTP). OpManager does not support this functionality, and we don't really have a timeline on when ZTP functionality will be available. In ManageEngine NetFlow Analyzer, we have to set custom thresholds to get alerted if there is a problem in network connectivity. It would be helpful if we could automate the tool such that we don't have to set thresholds manually, and the tool automatically alerts us when it detects issues. When experts deploy this tool, we already know what thresholds should be normal. But customers in general may not have this skill set. For newer customers who need to adopt this product, an automated method of alerting would definitely be beneficial.
Network Troubleshooting identifies, diagnoses, and resolves network issues to maintain seamless connectivity and performance. It's a crucial process in IT infrastructure management, ensuring optimal operation and minimal downtime.Maintaining a well-functioning network is essential for businesses to ensure their operations run smoothly. With the increase in complex network architectures, effective troubleshooting tools and methods are necessary. Quick identification of issues not only reduces...
The single biggest friction point I experience with ManageEngine NetFlow Analyzer comes down to database storage management and disk space explosion, as flow data records literally record every single conversation passing throughout the monitored interfaces. The volume of incoming logs is absolutely massive, so if I do not stay on top of the backend settings, the tool can easily choke the server. ManageEngine NetFlow Analyzer is absolutely a powerhouse for traffic forensics, and using it heavily day-to-day definitely highlights a few gaps where I end up thinking I wish it just did that natively, such as native built-in traffic shaping or direct remediation. If I could change one thing about ManageEngine NetFlow Analyzer, it would be transforming the tool from a purely observational platform into an actionable, active remediation tool. When I am sitting inside the ManageEngine NetFlow Analyzer dashboard and spot an internal machine maxing out one link, the tool does a flawless job of showing that I have a culprit, but that is where its job ends. To fix it, I have to break my concentration completely, leave ManageEngine NetFlow Analyzer, and pull up the SSH terminal to log in to the specific switch or the router CLI and manually apply a rate limit or drop the connection.
I would like better or easier integrations to extend its usefulness.
ManageEngine's product has some performance issues. It runs very slowly when the system is large and does not support high availability for big flow and high-level operations. The product needs improvement in supporting high availability for active-passive or active-active configurations when building for a large system. The price could be improved.
Sometimes customers are unaware about their own network. For example, we need SMTP credentials for Layer 2 switches to do automatic discovery of network devices. Sometimes the network management teams are unaware of their SMTP credentials because the teams have been shuffled since the network was deployed. Or sometimes, when we support our government and defense customers, they don't have clearance to share these credentials with us. Some of the features, such as auto discoverability, get hampered if the customer is not aware of their own network or somehow can't share privileges and credentials with our tool for them to work properly. Not in ManageEngine NetFlow Analyzer in particular, but there are other features of the OpManager suite that could afford to be updated. There is something called a CLI, command-line interface, that allows us to configure network devices such as switches. This is old technology. This product suite has CLI-based configurations, but as of last year, most network devices come with Zero Touch Provisioning (ZTP). OpManager does not support this functionality, and we don't really have a timeline on when ZTP functionality will be available. In ManageEngine NetFlow Analyzer, we have to set custom thresholds to get alerted if there is a problem in network connectivity. It would be helpful if we could automate the tool such that we don't have to set thresholds manually, and the tool automatically alerts us when it detects issues. When experts deploy this tool, we already know what thresholds should be normal. But customers in general may not have this skill set. For newer customers who need to adopt this product, an automated method of alerting would definitely be beneficial.