Server Management Software

The number of tools available in one centralized management hub is excellent. We use this management and monitoring system daily for our clients, and as an MSP supporting many organizations, it makes serving our customers much simpler.

With alerts, automations, scripts, custom fields, and NinjaOne Remote with behind-the-scenes access, we can quickly find device information and keep tabs on overall health. The areas we most commonly implement for our organizations are RMM, endpoint management, and patching. We’ve also started expanding into other services, such as MDM and NinjaOne Connect, and once you learn each module, they’re easy to roll out across the board.

Whenever we need assistance, customer service is quick to respond and, when necessary, escalates to qualified technicians for the specific scenario. Review collected by and hosted on G2.com.

Overall, NinjaOne has been a very effective solution for MSP technicians like me at Acruity. That said, there are a couple of issues I’ve noticed while using Ninja.

The first is Apple patching. Patching on Apple devices (macOS, iOS) has been somewhat inconsistent, both in terms of success and in how statuses are reported in Ninja. When reviewing patching activity, we’ve often seen cases where the status of whether updates were successful shows as unknown.

Another area I’d like to see improved is visibility for MSPs into endpoint errors and alerts. At times, it feels like NinjaOne representatives can pull more detailed information from the back end than we’re able to access on our side. More transparency into what’s happening would likely save time for both MSPs and support. That said, if there’s a security reason this information isn’t generally available to MSP technician accounts, I understand. Review collected by and hosted on G2.com.

To enhance the user experience, it would be beneficial to improve the consistency of Apple patching and increase transparency for MSPs regarding endpoint errors and alerts. Additionally, providing more detailed access to backend information could streamline operations and save time for both MSPs and support teams. Review collected by and hosted on G2.com.

Keeping track of a multitude of client devices without a centralized management system is nearly impossible. NinjaOne gives MSPs the ability to track and manage hundreds of devices efficiently and thoroughly. With Ninja, we can respond to offline server alerts as soon as they come in. We can also review endpoint patching and quickly address computers that experience patching failures. When we need to run commands on a machine while a user is actively working on it, Ninja lets us run those commands in the background without interfering with the user. Overall, Ninja saves time for both us and the client, while reducing interruptions and keeping day-to-day management smoother. In down client scenarios, we are able to use ping monitors and server network availability to get a lead on the source of the issue and act accordingly. Review collected by and hosted on G2.com.

LogRocket is most useful for us when a problem only makes sense after we’ve seen the exact sequence of state changes that led up to it. Being able to record Redux state and actions gives us that missing context, and pairing it with Frontend Performance Monitoring, heatmaps, clickmaps, rage clicks, and dead clicks helps us uncover issues that never throw a JavaScript exception. A page can return 200 on every request and still feel broken if a button looks clickable but does nothing, or if the interface takes too long to become usable. Because LogRocket captures performance, network activity, console logs, and user behavior through the same SDK, we can usually tell pretty quickly whether we’re dealing with a technical failure, a usability problem, or simply a confusing interaction. Product Analytics adds another helpful layer when the issue shows up inside a funnel: we can spot the drop-off, isolate the sessions that didn’t convert, and jump straight into replay instead of comparing dashboards across tools and then manually hunting down the same users. Review collected by and hosted on G2.com.

One downside is that LogRocket can surface more information than you realistically know what to do with. If the team starts opening random replays just hoping to “find something,” it quickly becomes a very expensive way to watch people use the product. We’ve seen much better results when we begin with a concrete signal—an error, a funnel drop, an affected user, or a Galileo insight—and then use the session replay as supporting evidence, rather than treating the replay itself as the investigation. Review collected by and hosted on G2.com.

N/A Review collected by and hosted on G2.com.

After a checkout change, support started getting reports that the payment button “did nothing.” Our automated tests were still green and there was no obvious exception, so the issue felt frustratingly vague at first. We filtered LogRocket sessions by the checkout URL and network failures, and quickly spotted users clicking the button over and over while one request was returning a 409 because the cart state had gone stale. In LogRocket’s Network Logs we could see the response clearly, and the timeline made it obvious how that network behavior lined up with our frontend state: Redux had left a loading flag stuck on, so the component never returned to an interactive state. From the user’s perspective, it really did look like a dead button. We fixed the reducer, added a more specific error message, and then reviewed the same funnel again to confirm the rage clicking had actually disappeared. LogRocket saved us from having to ask the customer for yet another screen recording, connected network activity and frontend state in one place, and let us validate the fix using real sessions instead of calling it done just because it worked locally. Review collected by and hosted on G2.com.

Yes, still lagging issue is facing. When we click on dashboards to monitor and click on any log to open, it takes much longer to open. Rest all things seems good. Review collected by and hosted on G2.com.

Any infrastructure related issues, Application response time related issues can be identified and alerted to specific people very smoothly and timely. Review collected by and hosted on G2.com.

The combination of Tracing, Logs, and Application Metrics is what moved Sentry beyond basic error monitoring for us. Since the .NET SDK began supporting metrics and Application Metrics became generally available, we’ve been able to track counters, gauges, and distributions, break them down by attributes like region or plan, and then pivot from an anomaly straight into the related trace, log, or error—without having to manually line up timestamps across multiple systems. We ran into this recently when auth failures started creeping up. The metric made the trend obvious, but the real value was being able to jump into the affected requests and see exactly where the failure was occurring. Monitors & Alerts have also become easier to manage because the signal and the notification path can be handled separately. A threshold can create an issue with the right context, while Slack, email, or PagerDuty routing is maintained independently. That separation helped us eliminate several duplicated alert rules that had slowly accumulated across projects. Cross-Event Querying is another feature I’m using more during technical reviews now, not only after incidents. Being able to search across spans, logs, and metrics makes it much easier to investigate a suspicious pattern early, before it turns into something urgent. The API improvements around traces, profiles, and attachments have also been helpful when we want to pull parts of that investigation into our own internal tooling, rather than forcing every workflow through the dashboard. Review collected by and hosted on G2.com.

Sentry has grown into a much bigger product than it was a few years ago. Issues, Explore, Traces, Logs, Metrics, Profiles, Releases, Monitors, and Seer add a lot of depth, but that breadth can also feel disorienting for a developer who opens the platform simply trying to understand a single exception. I’d prefer the initial experience to adapt more clearly to the task at hand, rather than immediately exposing the entire observability surface. Review collected by and hosted on G2.com.

We really saw the value of the full stack when an ASP.NET Core release introduced a regression that only affected customers with a specific configuration. The first sign was a slight uptick in 500 errors—noticeable, but not enough to trigger our usual infrastructure alerts. In Sentry, the exceptions were grouped in a way that made the pattern clear: the affected users shared the same feature flag and the same release. From the issue, we opened the trace and could see the request spending far longer than expected in a SQL call before it ultimately failed. Suspect Commit then narrowed our search even further by pointing us to the refactor where configuration loading had changed, which gave us a much smaller area to investigate. After we shipped the fix, we used Application Metrics to confirm the error rate returned to baseline, rather than assuming the incident was resolved just because the deployment completed successfully. We also realized our original alert was too sensitive and kept notifying on transient failures, so we replaced it with a Monitor that accounted for both rate and volume. Sentry didn’t eliminate the debugging work, but it did put the error, trace, release, and user impact on a single investigation path. That reduced the time we normally spend correlating logs across services and gave us a much better way to prove the fix actually worked in production. Review collected by and hosted on G2.com.

We really saw the value of the full stack when an ASP.NET Core release introduced a regression that only affected customers with a specific configuration. The first sign was a slight uptick in 500 errors—noticeable, but not enough to trigger our usual infrastructure alerts. In Sentry, the exceptions were grouped in a way that made the pattern clear: the affected users shared the same feature flag and the same release. From the issue, we opened the trace and could see the request spending far longer than expected in a SQL call before it ultimately failed. Suspect Commit then narrowed our search even further by pointing us to the refactor where configuration loading had changed, which gave us a much smaller area to investigate. After we shipped the fix, we used Application Metrics to confirm the error rate returned to baseline, rather than assuming the incident was resolved just because the deployment completed successfully. We also realized our original alert was too sensitive and kept notifying on transient failures, so we replaced it with a Monitor that accounted for both rate and volume. Sentry didn’t eliminate the debugging work, but it did put the error, trace, release, and user impact on a single investigation path. That reduced the time we normally spend correlating logs across services and gave us a much better way to prove the fix actually worked in production. Review collected by and hosted on G2.com.

There are only a few things that I was not satisfied with Datadog, those are. Cost is somewhat high; we have to pay even we utilize the resources or not.

And the main con is the customer support; they only deal via email, and we have to dump the log data into their storage. They first analyse the logs and come back to us; it will typically take 24-36 hours, which has an impact on the clients. Also, they only come on a call on production issues. Review collected by and hosted on G2.com.

Wide range, like we need to sit in front of the servers or app all the time. If there is any error, it will send an email or notifications regarding the error. So no need to worry. Review collected by and hosted on G2.com.

CubeAPM doesn’t have an app monitoring module as of yet. Review collected by and hosted on G2.com.

CubeAPM helps us detect and resolve performance issues across our e-commerce platform before they affect customers.

Earlier, we struggled with identifying slow APIs, checkout delays, and backend errors during traffic peaks. With CubeAPM’s unified visibility across metrics, logs, and traces, our teams can now pinpoint the root cause instantly.

The biggest benefit has been a noticeable drop in incident resolution time (MTTR) and smoother customer journeys during sale events. Review collected by and hosted on G2.com.

I don't like how I can't really customize status.xocat.online, so that could be improved. I mostly don't like the customization because I have to pay to access that, but it would be great if we could build our own website instead of just being stuck with Better Stack's template, even if it was paid. Review collected by and hosted on G2.com.

I use Better Stack to monitor my website's downtimes, saving me from having to build my own monitoring site, which I couldn't do. It's invaluable as it informs both me and my users about site issues. Review collected by and hosted on G2.com.

Sometimes the website will just not load, and I have to wait quite a few times. Also, Metric Explorer sometimes crashes if it has a tad bit more data to share. Review collected by and hosted on G2.com.

I use Coralogix for monitoring logs, alerting, and tracing, enhancing developer work and on-call team efficiency. It also optimizes costs with the TCO optimizer and integrates seamlessly. Review collected by and hosted on G2.com.

While there are some hiccups with Splashtop, I have a backup solution just in case, but the Splashtop integration works 95% of the time. It's still annoying when it drops, even though the workstation says it's online. We tried Copilot licensing through Atera early upon release, but it didn't function as we expected. We got up with support, who fixed the issue, but we haven't really dove in with regards to using AI with Atera because of the experience we had. Review collected by and hosted on G2.com.

Adelin is currently working with us on a weekly to bi-weekly schedule to help us refine our Atera experience and tailor it to exactly what we need. Concerning performance, I'd say it rivals the majority of RMMs out there, but being a lot smaller than some of the big RMMs, not as many resources can be put toward roadmaps, but every suggestion we give, I feel is taken to heart and pushed up the chain to the developers to see if there's an option for implementation. At one point, we were considering moving away from Atera and to Kaseya Ops, but since diving into our own "flavor" of Atera, we are slowly molding it to be exactly what we need it to be and it's nice knowing that support is behind us 100%! Review collected by and hosted on G2.com.

ServiceNow ITOM has a few notable drawbacks, starting with its high cost, particularly if you rely on advanced modules such as Discovery, Service Mapping, and AIOps. In large scale implementation projects, the implementation process can be complex and time-consuming, often requiring skilled resources as well as ongoing tuning to keep everything working as expected. In more complex environments, Discovery and service mapping may not always be fully accurate, which can lead to gaps or inconsistencies.

The platform also comes with a steep learning curve. On top of that, the AI/AIOps capabilities depend heavily on having high-quality data and the right configuration; early on, they may generate false positives or miss certain issues. Finally, performance can be impacted when large volumes of events are being processed, especially if the environment is not properly optimized. Review collected by and hosted on G2.com.

ServiceNow ITOM helps address several common challenges in IT operations, such as limited visibility, fragmented toolsets, alert overload, and overly reactive incident handling. By offering unified monitoring and service mapping, it provides clearer insight into infrastructure dependencies and supports faster root-cause analysis.

Thanks to its strong integration capabilities, ITOM can consolidate data from multiple monitoring tools into a single platform, reducing silos and improving coordination across teams. It also remains reliable under high event volumes, which helps teams process alerts efficiently and focus attention on what matters most.

With its AI/AIOps features, ITOM further reduces noise and inefficiency by correlating events, detecting anomalies, and predicting potential issues before they affect users. This helps shift operations from reactive firefighting to a more proactive approach.

From a pricing and ROI standpoint, the platform delivers value by reducing downtime, minimizing manual effort, and improving overall operational efficiency, which can translate into cost savings over time. In addition, structured support and onboarding make adoption smoother and help teams accelerate time to value.

The UI/UX is intuitive and well-structured, making it easy to navigate between events, service maps, and incidents, which improves efficiency and reduces the learning curve for operations teams. Review collected by and hosted on G2.com.

I find the licensing and pricing model complex, and it's sometimes difficult to predict as our environment scales. There's a learning curve for new users due to the large number of features and configuration options. Creating highly customized dashboards and reports can sometimes be less intuitive than expected. Improving ease of use, reporting flexibility, and cost transparency would definitely make the overall experience better. The main areas of improvement are pricing and transparency, ease of onboarding for new users, and more intuitive dashboard customization. While the platform is very powerful, simplifying access would enhance my user experience. Review collected by and hosted on G2.com.

I use Dynatrace for application performance monitoring and infrastructure monitoring. It analyzes logs, detects issues proactively, performs root cause analysis, and offers end-to-end visibility. This helps reduce downtime, improve system reliability, and ensures application health, user experience, and resource utilization are well managed. 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.

One area I dislike about ManageEngine Endpoint Central is that the interface can sometimes feel cluttered and overwhelming, especially when navigating through advanced features. Some configurations require multiple steps, which can make routine tasks more time-consuming. Improving the UI, simplifying navigation, and providing clearer guidance for certain settings would make the overall experience more user-friendly and efficient. Review collected by and hosted on G2.com.

ManageEngine Endpoint Central helps solve the challenge of managing and securing multiple devices from one centralized platform. It makes tasks like software deployment, patch management, remote troubleshooting, and device monitoring much easier. This saves time, reduces manual work, and helps ensure that endpoints stay updated, secure, and compliant. Review collected by and hosted on G2.com.

The main downside of OpManager Nexus is the upfront effort required to tune alert thresholds so you don’t end up with notification overload. Some of the deeper configuration areas—such as custom SNMP rules and report templates—also feel cluttered and harder to navigate than the primary NOC views. In addition, on-premise installations can demand substantial hardware resources, since telemetry data accumulates in the database over time. Review collected by and hosted on G2.com.

OpManager helped us address three major business challenges:

Pricing / ROI: It replaced our expensive legacy monitoring tools with a more cost-effective, device-based licensing model, which significantly improved our return on investment.

Support / Onboarding: Its automated discovery features made onboarding quick and painless, and we were backed up by responsive vendor customer service.

AI / Intelligence: The machine-learning adaptive thresholds reduced our alert fatigue by automatically distinguishing genuine anomalies from routine traffic spikes. Review collected by and hosted on G2.com.

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.

So far, I haven't found any drawbacks. Review collected by and hosted on G2.com.

It guarantees me a completely stable network. Previously, I had many wifi problems; when working with a large volume of data for my job, my NAS server did not function as smoothly and reliably as it does now. Review collected by and hosted on G2.com.

One area that could be improved is how complex it can be to configure and troubleshoot certain monitoring parameters and custom metrics. Some of the more advanced features may require extra setup steps or a higher level of technical understanding than expected. Clearer user guidance and stronger documentation, along with a more streamlined configuration process, would make the platform even more user-friendly and efficient. Review collected by and hosted on G2.com.

Site24x7 helps us address the challenge of continuously monitoring and managing a large IT infrastructure by giving real-time visibility into servers, networks, databases, applications, and other critical components. It enables us to spot issues early with proactive alerts, pinpoint potential performance bottlenecks, and cut down the time spent on troubleshooting. As a result, our incident response improves, downtime is minimized, and our team can maintain stronger overall infrastructure availability and performance. Review collected by and hosted on G2.com.

It's very difficult to find something to dislike, because I feel confident that anything we would want changed, the Netbeez team would be able to accommodate it. Review collected by and hosted on G2.com.

Our organization's workers are primarily remote, and their roles very often are ones that don't come with a necessary proficiency in technology. Therefore, it is often the case that home internet/router diagnosis falls entirely on us. This tool is essential to being able to gather objective troubleshooting data among the sea of subjective reporting we get from our users to determine where the actual cause of network interruptions lies. Review collected by and hosted on G2.com.

Updates some functions is better in real time. Review collected by and hosted on G2.com.

Better Traffic Engineer in our network. Review collected by and hosted on G2.com.

Nothing major to report so far—the platform works as expected. One minor suggestion: more detailed documentation around custom metrics would be helpful, especially for setting them up and understanding how they’re meant to be used. Review collected by and hosted on G2.com.

We use Dash0 as an independent platform to verify DS24 Gateway. It helps us confirm that the system is working correctly by letting us view metrics, traces, and overall system state in real time. With Dash0, we can validate our setup without having to build and maintain our own observability infrastructure. Review collected by and hosted on G2.com.