Benchmark Software

The pricing model based on sensor count can become expensive as your environment grows. Every new device, interface, or metric you want to track adds up quickly, so scaling monitoring across multiple sites requires careful planning around sensor usage. Review collected by and hosted on G2.com.

Honestly, before PRTG we usually only realized something was wrong after it had already impacted users. A lot of it came down to manual checks and guesswork. Now, with the alerts we’ve set up, we get an early warning before things go south—whether it’s a server running low on disk space, a slow link, or a device that stops responding. That has already saved us more than once from a real incident. It takes a lot of stress off the team because we’re not constantly firefighting anymore. Review collected by and hosted on G2.com.

What I like less are the presentations and the reports; they are somewhat cumbersome and, well, content-wise okay, but could be better in terms of presentation. When creating reports and adding content, error messages sometimes occur, and the format often needs to be adjusted so that, for example, the display in the PDF does not have certain tables exceeding one page, and similar, more visual things. Review collected by and hosted on G2.com.

I use checkmk for monitoring and inventory analysis; it quickly reports issues like CPU or disk usage. It helps to intervene proactively and automatically opens tickets, which is especially useful when different departments work together. Review collected by and hosted on G2.com.

I feel that the learning curve for configuring alerts and custom dashboards is steeper than expected, and the documentation does not always cover specific day-to-day scenarios. In environments with many devices, some screens are slow to load, especially when querying long periods of history. Review collected by and hosted on G2.com.

We had difficulty quickly determining whether a slowdown or outage was in the network, the carrier's link, or the application, and diagnosis relied on manual checks across various equipment. With SolarWinds, we can monitor in one place the bandwidth consumption, peak usage, and status of links and devices. This helps us identify circuit saturation, validate stability after incidents, and verify link behavior with historical data. The result is faster troubleshooting, with less perceived downtime for the user and more substantiation when contacting carriers and other teams. Review collected by and hosted on G2.com.

One area I feel could be improved is how Icinga handles monitoring workloads during satellite maintenance or failover, particularly in large environments.

We have locations where a satellite pair is responsible for monitoring close to 1,000 hosts and several thousand services. When one satellite is taken down for patching or maintenance, the remaining satellite has to handle the monitoring workload. This can lead to sudden spikes in check execution and resource utilization, especially when a large number of checks are scheduled around the same time.

Because of this, we have to plan satellite maintenance carefully to avoid overloading the remaining node. Better workload distribution and smoother handling of check execution during failover would make a real difference in larger deployments.

Another area I'd like to see improved is the dashboard experience in Icinga Web 2. While users can create their own filtered views, having centrally managed dashboards that can be shared with teams or made available to all users would be much more practical. In a global environment like ours, it would help us provide consistent monitoring views without everyone having to configure their own filters.

Overall, Icinga works well for our requirements, but improvements in these areas would make day-to-day operations easier, especially for teams managing large distributed environments. Review collected by and hosted on G2.com.

One of our main challenges is maintaining reliable monitoring across a global infrastructure with different technologies, network zones and security requirements. Icinga's distributed architecture fits our environment particularly well, including restricted and isolated network segments where direct connectivity to central systems is limited. We can execute monitoring checks locally through satellites while maintaining centralized visibility across our infrastructure.

Automation has also made a big difference in our daily operations. We've integrated Icinga with AWX and our existing infrastructure workflows, allowing us to automatically deploy monitoring agents, onboard new servers and remove systems when they are decommissioned. This has reduced manual effort and helped us maintain consistent monitoring standards across different locations.

From an operational perspective, Icinga helps us detect service failures, resource issues and application problems early, giving our teams an opportunity to investigate and resolve them before they develop into major incidents. Features such as direct SSH access from our monitoring interface, custom actions, acknowledgements and scheduled downtimes also make troubleshooting and routine maintenance more convenient for our operations teams.

What I particularly value is that Icinga is flexible enough to work with our existing infrastructure and operational processes rather than forcing us to change how we manage them. It gives us centralized visibility, supports our automation requirements and helps our teams respond more effectively to issues across a complex enterprise environment. Review collected by and hosted on G2.com.

The main areas I feel could be improved in ManageEngine Applications Manager are related to performance, usability, troubleshooting, and customization in complex MSP environments.

- Probe performance and scalability: Large monitoring environments with a high number of monitors can sometimes require careful capacity planning and tuning.

- Alert/alarm reliability: In some situations, alerts may require additional validation or troubleshooting to understand why an alarm was not generated as expected.

- Dashboard customization: Creating highly customized business dashboards can sometimes require additional configuration or integration effort.

- Reporting flexibility: Standard reports are useful, but certain client-specific reporting requirements may require additional customization or external tools.

- Troubleshooting complexity: Some application-level issues require deeper investigation through logs, database queries, or OEM support rather than being immediately identifiable from the console.

- Third-party integrations: Integrations with external tools can sometimes require additional configuration, API knowledge, or OEM support.

- Documentation: More detailed, scenario-based troubleshooting documentation for complex production issues would make it easier for L1/L2 teams to resolve incidents independently.

Overall, I find the product useful, but improvements in scalability, alert reliability, dashboard flexibility, reporting, and troubleshooting visibility would make it even more effective for large MSP and enterprise monitoring environments. Review collected by and hosted on G2.com.

ManageEngine Applications Manager helps solve key challenges in application and infrastructure monitoring by providing centralized visibility into the health, availability, and performance of business-critical systems. It helps us identify performance bottlenecks, detect issues proactively, monitor servers, databases, application servers, APIs, URLs, JVMs, and services, and reduce the time required for initial troubleshooting.

In our MSP environment, it supports monitoring across multiple client infrastructures through a probe-based architecture. Automated alerts, configurable thresholds, dashboards, and reports help our team respond to incidents more efficiently, improve SLA adherence, and provide better visibility to clients.

Overall, it benefits me by improving monitoring operations, reducing manual effort, enabling faster incident identification and escalation, and supporting better decision-making through performance metrics and reporting. It also helps me manage the monitoring team more effectively and maintain service availability for business-critical applications. Review collected by and hosted on G2.com.

One area where Zabbix could improve is its initial configuration and learning curve. Setting up custom templates, complex triggers, dashboards, and advanced monitoring items can require considerable technical knowledge. Sometimes troubleshooting incorrect item configurations and fine-tuning alert thresholds also takes time. The reporting and dashboard customization process could be more intuitive for administrators managing large infrastructures. Better built-in guidance, simpler configuration workflows, and more advanced AI-assisted troubleshooting would make the platform even more user-friendly. Review collected by and hosted on G2.com.

Zabbix provides centralized monitoring of servers, network devices, and IT services through agents, SNMP, APIs, and custom scripts. Its real-time monitoring capabilities help track CPU, memory, disk utilization, network performance, and service availability. This allows us to identify potential issues early, improve infrastructure reliability, and reduce downtime. Its open-source licensing significantly reduces monitoring costs compared to many commercial alternatives, providing excellent value for organizations managing large IT environments. The platform also supports extensive integrations and automation, while its documentation and community resources help administrators with implementation and troubleshooting. AI-powered root cause analysis and predictive insights could further improve its capabilities. Review collected by and hosted on G2.com.

I find that Pandora FMS remains primarily a monitoring tool: it displays received information and triggers alerts, but allows little direct action on services or equipment remotely, for example, to restart them. I would like to be able to add configurable command buttons in the agent or in one of its values, to launch Python scripts. Review collected by and hosted on G2.com.

With Pandora FMS, I can very easily see the status of servers, services, and physical equipment for all our clients. Review collected by and hosted on G2.com.

The initial configuration and setting of alert thresholds can take time. A more guided approach would help limit unnecessary alerts and focus on priority incidents. Review collected by and hosted on G2.com.

It allows for the detection of downtimes and performance degradations without manually checking each piece of equipment. Centralized supervision helps identify affected services, prioritize interventions, and reduce incident resolution time. Review collected by and hosted on G2.com.

Pricing models are based on data ingestion volumes, if the size of the data increases heavily, then the cost will also increase very heavily. Maintenance burden will also be very high since we are ingesting all data at one place. Review collected by and hosted on G2.com.

In this Splunk instance we collect, report, and analyze data related to the devops-managed cloud environments. Since the data become centrally available it becomes very easy to analyze the logs, checking security threats, creating report for account specific data. We have a full control over the infrastructure and it a very high speed data searching. If we find anything vulnerable then we raise ticket immediately to the concerned team in Jira automation. Review collected by and hosted on G2.com.

The only thing I would suggest to improve is the service reliability. There are a few instances where we have to restart the services when monitoring drops out. Review collected by and hosted on G2.com.

Problem: In modern applications built using microservices architecture, monitoring each service individually and understanding their interactions can be complex and challenging.

Solution: Instana provides automatic discovery and mapping of microservices, offering visibility into the entire application stack. This simplifies monitoring and troubleshooting in microservices-based environments. Review collected by and hosted on G2.com.