In terms of network troubleshooting, not so long ago a new company started (IT hosted on our location), and one of them was complaining about QoS trouble with VoIP telephony. They decided to go with a cloud telephony solution where I did have no say in it. I had to tell them, "I have no idea how this thing works. I have no visibility into any of the management of that solution." They were complaining about bad voice quality. Normally, I shouldn't have been able to know anything about it. But I thought I would just put Skylight on it for a moment to have a look at what was happening. I changed the mirror for a while so that Skylight could see the traffic, and it didn't take long to figure out that there were a few agencies that the company was using that had, at certain moments in time, some notable packet loss and some bad MOS scores on the VoIP part.
With that information, I was able to go to the company that gave us the SIP trunk and tell them about it. They changed some parameters, because there was something wrong on their side, and it was fixed.
Without that hard information it would have been pretty difficult to find things like that. Skylight is not used on a daily basis, but when it's used it usually helps to fix a problem pretty fast. I don't really have to look into multiple devices because it captures most of them. With that information I can usually say, "Okay, why is your server slow? Maybe you should not have all the thin clients asking every ten seconds about some server." If you have 1,000 thin clients, suddenly you have 100 requests every second.
That's what you can easily see with Skylight.
I have no idea how much time it has saved when it comes to response time, but I am comfortable saying "a lot."
In terms of helping improve interaction between our network, server, desktop and database teams, we're all in the same boat. It has helped me a lot when they have had serious issues. It helps me to say, "You came to me with an issue, I found this information. Which points to a specific problem at some team". It helps them, of course, in figuring out why something is slow/not working... It helps us saving time. We can look for a solution, not the problem.
In the past, we had some serious loads on a file cluster, which was mainly due to a few procedures doing some bad things, like passing through an entire directory and asking for every file in the directory tree one by one. While doing that, it continually opened and closed all the total transactions. So it was incredibly slow and incredibly heavy, because of one bad procedure. Skylight helped us a lot at that point in time, especially the server team, to figure out why the file cluster was slow. In the end it was a simple procedure creating havoc on the FILE Cluster. Hard to find when you can't see CIFS traffic.