Improve Citrix login times by as much as 500%
Reduce time spent troubleshooting problems by 50%
Save $354,500 annually on troubleshooting and diagnosis
The IT organization at Seattle Children's Hospital supports more than 100 applications for over 8,500 users across 25 different physical locations. "We've got an environment with just about every technology you could think of," says Tim Holt, Senior Director of Enterprise Architecture. "And consequently, it's very, very difficult to troubleshoot performance from an end-user perspective."
After ExtraHop found the "ghost" in my VDI machine in a matter of hours, I was a believer ... If you're going to do VDI, don't do it without ExtraHop.
Wes Wright CIO, Seattle Children's Hospital
Seeking greater visibility, Seattle Children's turned to ExtraHop for something none of their traditional monitoring products offered: the ability to tap into a wealth of wire data flowing through their environments. Wire data is all L2- L7 communications between systems, including full bidirectional transactional payloads.
Seeing How Apps Really Work
For the first time, Seattle Children's had the cross-tier visibility to put troubleshooting issues in context.
"I've never seen anything comparable to ExtraHop," says Bruce Fulton, Senior Systems Infrastructure Team Engineer. "It's our way to see how a transaction flows from start to finish through these various applications. We simply couldn't get that end-to-end perspective with any of our previous technologies."
"We're familiar with network sniffers and so forth," adds Holt. "But those things only give you raw data, not the contextual associations across tiers as you have with ExtraHop."
No More Blind Troubleshooting
Before ExtraHop, the IT infrastructure team was forced to follow a time-consuming, "guilty until proven innocent" approach to troubleshooting, spending 20% or more of their time trying to diagnose non-obvious problems. ExtraHop cut that in half.
"We always found ourselves trying to prove that a problem wasn't coming from a particular technology silo," says Holt. "We'd start with the network team, who would burn a whole bunch of time proving the network was operating as expected, and then you'd move on to the next level of the stack. 'Well, it's not here, must be somewhere else.'"