Customers usually use SolarWinds Hybrid Cloud Observability for infrastructure monitoring. Cloud and on-premises monitoring is something that we can do with SolarWinds Hybrid Cloud Observability. Beyond that, application service monitoring is also part of it. We are trying to use as much as possible the features that belong to SolarWinds Hybrid Cloud Observability native out of the box. Those include networking, so network devices, routers, switches, all of which are monitored using SolarWinds Hybrid Cloud Observability only.

Dashboards are the key thing in SolarWinds Hybrid Cloud Observability. When we are trying to look into the NOC team, or the command center, these are the dashboards that represent the uptime, downtime, and other things. Those are the things that are available at this point in time. While we are trying to present it to the management and try to get the insights, what is the trend? If that kind of reports needs to be generated for the last couple of weeks or a couple of months, we are having a hard time doing that. Live data is good for immediate action, specifically for the command center and the NOC team, but for the management, the live data is only a snapshot that they see at the current moment. However, they are more interested in the improvements or what has improved from the previous months. If we need to show that using SolarWinds Hybrid Cloud Observability dashboard, that is a challenge.

I participated in the initial setup of SolarWinds Hybrid Cloud Observability. As a manager, I was managing the team and they did all the configuration. I have been informed on how the things are done, how much time we took to deliver it, and how many devices we initially configured, but not at the level of how we configured them.

The dashboard and reporting can be improved. The way the dashboards are being configured and presented in SolarWinds Hybrid Cloud Observability has certain challenges. The look and feel and ease of configuring are areas where we see difficulties. There are certain limitations where we are not able to select the range or live details. Specifically, I want to have a trend analysis on certain thresholds, but those are tricky and we are not able to do that. We are currently downloading that and then using Excel to represent it. Those kinds of features are missing as of now.

AI features in SolarWinds Hybrid Cloud Observability, we only started this in 2024. We are still stabilizing the environment. AI is the next thing, so we did not start looking into that yet.

Even the dashboards that we are trying to build to understand the trend analysis in SolarWinds Hybrid Cloud Observability show always the live information. What is the current state, how many monitors, how many are green, how many are amber, where we have warnings, what are at risk, is the live information that we could build from the dashboard. When trying to analyze the thresholds or how much increase we need to make, or what the trend is happening, getting into those details is difficult. Building those kind of reports is a tricky one. We struggle a lot in that area.

ServiceNow is the primary thing for me. SolarWinds Hybrid Cloud Observability and these are all the add-ons that come into my portfolio where I look into these as well.

The stability of SolarWinds Hybrid Cloud Observability would be rated at 8 overall. Usually there are no issues. Once we have built it, we are currently running it on-premises. We only take it down for the usual upgrades that have been sent from SolarWinds Hybrid Cloud Observability. Beyond that, we do not see any problem with the monitoring. We have to put a lot of communication in place because if we are trying to take SolarWinds Hybrid Cloud Observability down for upgrades, then obviously the entire observability or infrastructure monitoring is paused. There is no monitoring happening when it is down. That is a risk factor. Currently the configuration is not configured for a high availability. The organization is okay to take one or two hours down in a quarter. With that, the patches that are being applied means the entire monitoring goes dark specifically. That is acceptable for the organization. That risk has been accepted.

The scalability of SolarWinds Hybrid Cloud Observability could be rated at 8. When we talk about scalability in SolarWinds Hybrid Cloud Observability, from the cloud perspective, the scalability is much easier. When we look from on-premises infrastructure, the scalability is not as easy as the cloud infrastructure because these are all physical servers. You have a physical node that adds capacity and we have the agents that we install or we have to choose whether to use agent-based discovery or agent-less discovery. We need physical servers that have to be deployed specifically. When we are talking about physical servers, there is a lengthy process on the scalability perspective. When it comes to cloud, it becomes pretty easy on the scalability. We could even program it to adjust the memory and the processing speeds that are required for that particular configuration. Technically looking from the hybrid model where we have physical on-premises and cloud infrastructure together, to balance that, I would rate it at 8.

The technical support of SolarWinds Hybrid Cloud Observability is okay. I would rate it 7 for the technical support. I do not interact with the technical team of SolarWinds Hybrid Cloud Observability. It is my team who regularly interact if required. I have not heard any complaints or escalations from them because there are very few scenarios where they reach out to the technical support. It is not a frequent thing that happens. What I understand from my team interacting with them is that the time duration that we get is not immediate. They take at least 24 hours or 48 hours to respond and communicate. For the current situation, it is okay. We do not find any urgency, so it is acceptable for us.

We are moving from a different tool. There are other observability tools such as ScienceLogic and Netcool. From there, we needed to get the devices into SolarWinds Hybrid Cloud Observability. Initially, we were able to build the entire setup within 15 days. The entire infrastructure setup of SolarWinds Hybrid Cloud Observability has been built. The next one and a half months, or let us say two months, is something that we were able to bring up all of the 5,000 servers including VMs, data, physical Windows servers, Linux servers, and network devices into SolarWinds Hybrid Cloud Observability. That is the initial time that we took to configure SolarWinds Hybrid Cloud Observability. All of that has been brought in within two months.

The deployment depends upon if we have cloud infrastructure heavily, then deploying it in cloud is more appropriate for SolarWinds Hybrid Cloud Observability. If we have more on-premises infrastructure, we should be going with a hybrid structure where nodes should be deployed. Currently, we have three nodes where we deployed it in three regions: Americas, EMEA, and Asia-Pacific. Similarly, if we have high utilization in cloud, we should be able to build one there in the cloud as well so that the pulling happens smoothly. It is all based on the infrastructure that we have, and we take the decision whether to put it in the cloud or put it on-premises.

SolarWinds Hybrid Cloud Observability is something that we have implemented for one of our customers, specifically on SolarWinds Hybrid Cloud Observability cloud platform. I am leading the team and the resources have freshly implemented SolarWinds Hybrid Cloud Observability. We are also managing SolarWinds Hybrid Cloud Observability tool and making sure the monitoring is happening and reports are getting generated. New infrastructure is getting added to SolarWinds Hybrid Cloud Observability for monitoring. Trying to consolidate other monitoring tools such as PRTG or other things and bring other application services as well as infrastructure into SolarWinds Hybrid Cloud Observability is the overall project and it is more than a year. It is not something that has been completed; it is a continuous process where the platform has to be managed, new infrastructure has to be brought in, application service has to be brought in, and we need to make sure that the thresholds and other things are being managed properly. These are a few things that do not end once we start the project; until we are supporting the customer, we continue to do the maintenance and administration and also bring new infrastructure into SolarWinds Hybrid Cloud Observability. This is a continuous process and the target is also to integrate SolarWinds Hybrid Cloud Observability with ServiceNow to get to the next level.

We need to find the right vendor for SolarWinds Hybrid Cloud Observability. If we directly reach out to SolarWinds Hybrid Cloud Observability, it is an expensive one. We reached SolarWinds Hybrid Cloud Observability in India, and CDW is where we reached in the UK. We have to think from the global perspective to determine which country is giving us more effective cost. When working for a global organization where we have business across the entire globe, we have certain leverages. Getting quotes from different regions means we could buy it from anywhere. Because it is a global organization, we should be able to pick from the right place so that we could gain the right costing and discounts that we could leverage.

SolarWinds Hybrid Cloud Observability is device-based. How many devices we want to bring on board determines the cost. Technically, we have built multiple clusters based on the regions that we want to locate. One is in the EMEA region, one is in Asia, and one is in the America region, and we have put them into the data centers. From there, the information gets pulled into SolarWinds Hybrid Cloud Observability. Based on that structure, the licensing would work. Based on the regions, the pricing and the vendor, the price quotations are different. We approached SolarWinds Hybrid Cloud Observability directly and the quotation that they gave was a very expensive one. We reached out to CDW and the price that CDW gave us is very effective and comes under our budget. We went to CDW and bought it.

This project started in November 2024 and is still continuing. Before that, there was almost 2013 to 2016, where we did the same thing. There is a gap in between, but in between there are other tools that we have jumped into. We do not say it is constantly working around with SolarWinds Hybrid Cloud Observability but on and off we see our profile update.

Network path visualization capabilities of SolarWinds Hybrid Cloud Observability remain unclear.

We utilize the platform's anomaly detection in SolarWinds Hybrid Cloud Observability. We only know that we are using that, but our team is the best team to talk about how we do that and what are the current challenges or things that bring value to that. We do not get into those details because we are managing multiple tools at our level.

Security of SolarWinds Hybrid Cloud Observability would be rated at 9. It is pretty strong because it follows all the protocols specifically covering the security space.