This is vital information - I had a case where my customer had a connection to a provider. When problems came up on Monday they, of course, said it was on the customer side. By using SolarWinds to inspect the path to the vendor I was able to quickly identify that the provider had 1 connection into their network on Friday and 2 on Saturday - the second connection was showing as down. When I reported that to the provider they acknowledged that they had indeed made that change but not updated routing.- without SolarWinds that would have been an all-day finger-pointing event.
We always think ignorance is bliss when we leave our responsibility in the hands of a service provider who often doesn't give a hoot about our equipment. I want to know all the things, even more so if i'm relying upon a third party to deliver it and who probably won't tell me if something goes wrong as they have their reputation to keep intact.
If we were in the cloud - we would definitely like to see the cloud provider's connectivity to our network. That is the most critical obstacle that I am going to face if and when the application goes in that direction. We have to have 5 9's in order to serve the public without disruption, no way could we go right now!
Let alone affordability to get to the 5 9's
When there exists lack of insight into a platform for which communication are critical, then monitoring fails our customers. When business operations are dependent upon hybrid communications, the bottleneck and single point of failure becomes the service provider. That is unacceptable. Customers and vendors depend upon our knowledge and insight to keep their services online and operational. Even for small businesses, service providers are a critical component of infrastructure for supply chain and life essential services delivery.
this would be fantastic. Today we use NATs to know some of this data. NBAR hels for the bigger companies.... but custom definitions would be a big benefit
alright
