Website Monitoring Software

I do dislike the delay in the live feature. Another dislike is an inability to display all users on an account, I have to search individually by email. This could be improved by potentially allowing a batch search filter or an easy way to add multiple criteria Occasionally the program will miss recording a session or doesn’t pick up that we have a user signed in and active which has caused some headaches. Review collected by and hosted on G2.com.

I am solving issues with a punchout system that is sometimes unstable, and I need to identify where a user is experiencing issues. The biggest benefit is not using another screen-sharing application since those are not always compatible with user systems. I am also able to see exactly what the site is doing which has allowed me to more accurately convey issues to our 3rd level support teams. Review collected by and hosted on G2.com.

While NinjaOne was more expensive compared to other RMM solutions our team evaluated, the professionalism and value it provides absolutely justifies the cost. Review collected by and hosted on G2.com.

NinjaOne is indispensable in our IT environment for its robust remote monitoring and troubleshooting capabilities. It ensures all company devices consistently adhere to the latest software and OS updates, maintaining compliance seamlessly. Furthermore, it enables instant remote access, enabling our team to promptly address and resolve any user issues. This significantly enhances our operational efficiency and user satisfaction. Review collected by and hosted on G2.com.

One thing that could be improved is the learning curve, especially for new users who are getting familiar with the platform. Some dashboards and configurations can take time to understand, and navigating large amounts of data can occasionally feel overwhelming. Simplifying the initial setup and making some advanced features more intuitive would make the overall experience even better. Review collected by and hosted on G2.com.

It helps us solve the challenge of monitoring complex systems and troubleshooting issues quickly. Instead of switching between different tools to analyze logs, metrics, and traces, we can get a more complete picture of what's happening in one place. This makes it easier to identify the root cause of issues, reduce downtime, and improve overall system performance. It also saves the team time and helps us make better decisions using real-time insights. 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.

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.

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.

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.

Some issues require site visits which have nothing to do with RMM. Review collected by and hosted on G2.com.

A lab PC is three months behind on Windows updates and failing a compliance check. Patching pushes the missing updates after hours, confirms they installed, and clears the flag without a campus visit. A front-desk machine is frozen mid-enrollment. Remote control puts you on the session in about a minute, you kill the stuck process, and the adviser stays on the phone with the applicant. Disk space on a shared workstation hits the alert threshold before the user notices. You clear the cache and the temp files from the console. The ticket never gets written. A laptop drops off the network overnight. The agent shows it last checked in, whether it is online now, and which switch port it was on. You know if it is asleep, unplugged, or actually down before anyone drives over. Review collected by and hosted on G2.com.

I think the main downside for me with Better Stack is the pricing. Initially, everything was great, but as our team grew and we needed to add access or addons for the status page feature, the costs started to climb. It seems a bit faster in terms of pricing increases than what a solo developer or a small team might expect. That was a bit of a con for me. Review collected by and hosted on G2.com.

I use Better Stack for downtime checks and incident alerts without needing a heavy setup. It offers a clean, simple dashboard, making it easy to monitor apps and fix issues quickly. Plus, it's generally better and easier than competitors and free to set up. Review collected by and hosted on G2.com.

1. Although dashboards have improved, certain configurations and investigations still require navigating through multiple screens. 2. The platform offers many apps, but new users need significant time for training to become comfortable with features like DQL, Grail, advanced dashboard creation etc.. Review collected by and hosted on G2.com.

1. Unified observability: Having logs, metrics, traces, RUM, Synthetic monitoring, and infrastructure data in a single platform makes troubleshooting more efficient. 2. Root Cause Analysis - The AI driven problem detection and automatic dependency significantly reduces the time required to identify the root cause. 3. End to End visibility - The ability to trace a user transaction from browser through application, services, database etc.. provides complete visibility into application performance and customer experience. 4. Additionally, the customizable dashboards, alerting capabilities and DQL make it easier to create reports and dashboards that can be shared with leaders/stakeholders. 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.

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.

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.

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.

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.

Reporting isn't good. Alerting setup is a bit complex. I had to dig through the documentation to get the email notification to work properly. Review collected by and hosted on G2.com.

A few months ago a sudden spike in one of our core network switches. Observium flagged the interface as saturated, and I tracked it back to a misconfigured backup job. Without Observium, I probably wouldn't have caught it until users started complaining. Review collected by and hosted on G2.com.

Not a dislike but a feature I would like to see is ExtraHop move towards prevention. Currently, the product is good at identifying and detecting suspicious or malicious activity. Prevention can be achieved through integration with tools but it would be nice to have these native to ExtraHop. Review collected by and hosted on G2.com.

Whenever we perform penetration tests, ExtraHop is always the first tool to detect the activity. Often times, the penetration testers will start their campaigns performing reconnaissance and trying to remain stealthy. Because they are not attempting to exploit vulnerabilities at this stage and may be using legitimate system tools, these actions would usually go unnoticed. By inspecting all network traffic, ExtraHop is quick to determine unusual activity on the network host even if it is not a managed device. The network traffic can be inspected by SOC teams and actions can be taken to contain the suspicious device. 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.