SolarWinds Observability SaaS

We used SolarWinds Hybrid Cloud Observability  for monitoring purposes. I was into server monitoring earlier. In that team, we had airline accounts and banking accounts. For server monitoring purposes, we used the HCO of SolarWinds for network performance monitoring and other tasks.

This was primarily a monitoring job. When I was in the monitoring team, we had different sets of teams working in shifts. Everything was installed, and we were the operators. At that time, we handled network performance monitoring, server application monitoring, database observability, log management analysis, cloud infrastructure visibility, and other insights.

SolarWinds Hybrid Cloud Observability  offers excellent features. It has end-to-end visibility, flexible deployment, and hybrid support from the support team. AI ops, scalability, and enterprise features for distributed environments, such as more polling engines, web servers, and high availability are very good in the HCO.

Before HCO, many organizations used multiple SolarWinds modules such as NPM , SAM , and WMAN. With SolarWinds Hybrid Cloud Observability , they gained a unified, single pane of glass view for the network, server, databases, and cloud resources. It reduced monitoring silos and enabled fast root cause analysis to easily identify what occurred during incidents. This improved collaboration between network, infrastructure, and application teams.

Reduced downtime and faster issue resolution are significant benefits of SolarWinds Hybrid Cloud Observability . Features such as PerfStack, NetPath, and intelligent maps allow organizations to visualize dependencies and pinpoint problems quickly. Mean time to detect (MTTD) and mean time to resolve (MTTR) have dropped significantly. Fewer war room calls and blame games occurred as teams now act on collaborated data instead of guesswork. One enterprise user reported an average incident resolution time improvement of 40% after consolidating their tools into HCO.

Currently, SolarWinds Hybrid Cloud Observability monitors AWS , Azure , and virtual environments, but it is primarily built on the traditional Orion platform. I think deeper integration into Kubernetes , serverless functions, and cloud-native tracing can be implemented as these matter to many organizations. Additionally, the user interface and modernization of the UX can be developed.

I used SolarWinds Hybrid Cloud Observability for approximately two to three years when I was in a different project.

I have not experienced any stability issues with SolarWinds Hybrid Cloud Observability. It performs well.

For SolarWinds Hybrid Cloud Observability's scalability, SolarWinds publishes scalability engine guidelines for large deployments. A single polling engine with enterprise supports up to 100 additional polling engines, monitoring up to 100,000 elements per instance. For large users, web servers and polling engines can be scaled. There are case studies of real customers showing growth and their ROI. The enterprise scale edition helps with scaling.

The customer support for SolarWinds Hybrid Cloud Observability is excellent.

Positive

Other tools from SolarWinds were used before SolarWinds Hybrid Cloud Observability. Netcool and other solutions were also utilized.

SolarWinds Hybrid Cloud Observability helped save time, money, and resources.

I do not have information about pricing, setup cost, and licensing for SolarWinds Hybrid Cloud Observability because those aspects were handled by a different team in the organization.

Before choosing SolarWinds Hybrid Cloud Observability, we evaluated IBM's solutions. Kyndryl , being a spin-off from IBM, provided other options. The product is made up of IBM, so they were explored.

Start with clear visibility goals, size your environment properly, start small and then expand, and invest in the database layer. I would recommend all these things to anybody who is trying to implement SolarWinds HCO.

On a scale of 1-10, I rate SolarWinds Hybrid Cloud Observability a 9.

Private Cloud

Other

After joining Accenture company, I have been directly using SolarWinds Hybrid Cloud Observability  for monitoring purposes for all network devices.

We are using SolarWinds Hybrid Cloud Observability  for network purposes to monitor network devices such as Cisco and firewall equipment.

We use SolarWinds Hybrid Cloud Observability  to monitor our network devices such as routers, switches, and firewalls. For example, if a router CPU or interface utilization goes above the threshold, SolarWinds Hybrid Cloud Observability  sends an alert. We then check the device's status, review performance graphs, and identify what's causing the spike, such as high traffic or a faulty interface. This helps us to take quick action before it impacts the user or they lose some connectivity on the interface.

Apart from monitoring network devices, we also use SolarWinds Hybrid Cloud Observability to track our performance, check application health, and review traffic trends. It helps us quickly find the root cause of issues by showing details, metrics, and logs in one place. We also use it to generate reports and share updates with the team.

SolarWinds Hybrid Cloud Observability has helped our organization stay on top of network and system performance. It allows us to spot and fix issues quickly, reducing downtime and keeping us happy. The clear dashboard, alerts, and reports make monitoring easier and save our team a lot of time. Overall, it has improved efficiency and given us better visibility across both cloud and on-premise environments.

All-in-one visibility in SolarWinds Hybrid Cloud Observability is one feature that stands out. It lets you monitor every server, application, cloud, and on-premises from a single dashboard. This is the main benefit. Smart Alert is also a valuable feature. We get a notification whenever any utilization goes high, an interface is down, a circuit is down, or BGP is down.

Smart Alerts in SolarWinds Hybrid Cloud Observability has been really helpful for our team. For instance, one day, a switch interface started hitting high utilization, which would have caused slowness in network traffic. SolarWinds Hybrid Cloud Observability sent an alert immediately, so we could check the devices and fix the issue before users noticed any problem. Without Smart Alerts, we might have found out much later, causing downtime or performance issues.

The dependency mapping feature is another notable aspect. It shows how devices and applications are connected, which helps us quickly find the root cause of a problem instead of guessing. We also find the reporting and historical data very useful. It helps track our trends over time and plan for capabilities or upgrades.

With SolarWinds Hybrid Cloud Observability, our team has been able to respond to issues much faster. Alerts let us fix problems before users are notified, which has significantly reduced downtime by around 30 to 40%. The dashboard and reports also save our team approximately two or three hours per day that we can now spend on other tasks. Overall, it has made our network management more efficient and proactive.

SolarWinds Hybrid Cloud Observability could be improved in several ways. It feels slow sometimes, especially when handling large amounts of data. The initial setup and configuration can also be complex for new users. If it were faster and easier to set up with simple dashboards for quick insights, it would be even better.

Customer support could be quicker and more responsive with urgent issues. Integration with third-party tools could be smoother, making it easier to connect with other systems we use. The dashboard could also be simpler for quick insights. More guidance or templates for new users would be helpful during onboarding.

Report customization is another area that could be improved. While the built-in reports are useful, being able to create more flexible and tailored reports would enhance our experience.

I have been using SolarWinds Hybrid Cloud Observability for two years at Accenture, where I joined as a fresher in the networking field.

I would rate SolarWinds Hybrid Cloud Observability eight out of 10 due to issues with speed and setup.

In our organization, SolarWinds Hybrid Cloud Observability is deployed in a hybrid cloud setup. It monitors both our on-premises systems and our cloud environments, such as AWS  and Azure .

We use both AWS  and Azure  with SolarWinds Hybrid Cloud Observability. Currently, we use Azure slightly more for our main workload, but AWS is also monitored for specific applications and servers. This allows us to keep track of performance and issues across both cloud environments.

We acquired SolarWinds Hybrid Cloud Observability directly from SolarWinds, and it's connected to our cloud and on-premises system. Our company does not have any other business relationship with SolarWinds besides being a customer. We are not a partner or reseller.

It's easy and quite simple, but SolarWinds Hybrid Cloud Observability could improve the interface to make it more useful. We should have an option for speed also. Overall, it's good.

Hybrid Cloud

Other

What do you like best about the product?

It is a comprehensive solution that covers a wide variety of monitoring requirements. From network devices, to traffic, to servers. Other aspects like storage, web performance, etc.
Secondly, the simplicity of using the product from a user perspective. It does not require you to edit any config files, or keep a track of files to set up and modify your monitoring needs

What do you dislike about the product?

Technical support or other resources available do not provide enough information or support for integrations using the SWQL studio. There should be resources available to learn, implement and troubleshoot integration issues.

What problems is the product solving and how is that benefiting you?

So far we dont have evey feature and capability of HCO being utilized, but the fact that it sits at the center of our ITSM, network, and other systems and provides a wide visibility of the infrastructure.

What do you like best about the product?

Ease of use and vendor agnostic useability.

What do you dislike about the product?

Setup can sometimes be confusing but, for the most part, is rather straightforward setting up.

What problems is the product solving and how is that benefiting you?

I like being able see view my environment easily within a single pane of glass.

What do you like best about the product?

SolarWinds Hybrid Cloud Observability (HCO) is like a stop for IT engineers for keeping an eye on everything on environment (like server, backup, storage, network, AP, Sensors, UPS etc) setup—either platform is running on-prem, in the cloud, or somewhere in between. Solarwinds pulls together monitoring for networks, infrastructure, apps, and cloud services into one easy-to-use and manage dashboards. We are currently managing 35K + devices and components under a single monitoring roof. It's becomes way simpler because of flexible licensing and smart alerts, it saves time and cuts down on admin work. If someone doesn't have hand-on experience on scripts and languages then he can easily use the manually features (like alert creation, report, any modification). HCO completely transformation and gives better visibility, on license, issues and keep things running smoothly.

What do you dislike about the product?

*here is a limitation from the tool that Dell does not expose much volume information over WMI hence we are unable to monitor the disk operations on the dell servers.

What problems is the product solving and how is that benefiting you?

* Flexible deployment options—on-premises, cloud, or hybrid
* Flexible Licensing (Combines multiple modules like Network Performance Monitor (NPM), Server & Application Monitor (SAM), Log Analyzer, IP Address Manager (IPAM), and more into a single platform)