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.
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.
The solution could improve in areas such as on-premises container monitoring, CICD observability, and providing additional documentation and support files in languages other than English.
The tool's escalation process needs improvement. More support is needed for the new generation of solutions, particularly SD-WAN support and newer storage components. Additionally, as more vendors move towards API-based monitoring, we anticipate SolarWinds HCO will increase integrations with other solutions. Another area for improvement is reporting. With infrastructure becoming increasingly diverse, the static infrastructures of the past are evolving into dynamic setups. Traditionally, we had wireless in the office, a backend Internet connection, and connections to head offices and data centers. With the advent of SD-WAN, multiple service providers, and cloud-based options, infrastructure is more dynamic. Today, most customers are not using on-premise solutions exclusively; they are opting for Office 365, G Suite, or similar services. Therefore, monitoring requirements are no longer limited to on-premise infrastructure but span diverse environments—some on-premise, some in the cloud. This is why SolarWinds is moving towards hybrid cloud observability. We would like to see more integrations and support for third-party vendors. For example, current support for Google Cloud Platform (GCP) is limited, and expanding this support would be beneficial.
Learn what your peers think about SolarWinds Hybrid Cloud Observability. Get advice and tips from experienced pros sharing their opinions. Updated: October 2025.
SolarWinds Hybrid Cloud Observability enhances IT operations with comprehensive visibility across hybrid environments for improved performance and uptime.Providing a unified platform, SolarWinds Hybrid Cloud Observability allows IT teams to manage, monitor, and optimize both on-premises and cloud resources. It integrates seamlessly with existing tools, improving efficiency with robust data analytics and visualization. Its advanced features decrease time-to-resolution for system issues and...
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.
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.
Event management features can be added as it has limited capability to ingest events from external sources.
The solution could improve in areas such as on-premises container monitoring, CICD observability, and providing additional documentation and support files in languages other than English.
The tool's escalation process needs improvement. More support is needed for the new generation of solutions, particularly SD-WAN support and newer storage components. Additionally, as more vendors move towards API-based monitoring, we anticipate SolarWinds HCO will increase integrations with other solutions. Another area for improvement is reporting. With infrastructure becoming increasingly diverse, the static infrastructures of the past are evolving into dynamic setups. Traditionally, we had wireless in the office, a backend Internet connection, and connections to head offices and data centers. With the advent of SD-WAN, multiple service providers, and cloud-based options, infrastructure is more dynamic. Today, most customers are not using on-premise solutions exclusively; they are opting for Office 365, G Suite, or similar services. Therefore, monitoring requirements are no longer limited to on-premise infrastructure but span diverse environments—some on-premise, some in the cloud. This is why SolarWinds is moving towards hybrid cloud observability. We would like to see more integrations and support for third-party vendors. For example, current support for Google Cloud Platform (GCP) is limited, and expanding this support would be beneficial.