We're just trying to identify the application interdependencies, which normally reside on different servers, including web servers, database servers, enterprise service bus, et cetera, up to your presentation layer before we start moving stuff around. 

Normally, the reason why we use these tools is to understand what assets we have, where they're deployed, and how they enter and operate before we decide to go move something from point A to point B. The solution is going to allow me to establish a wave or migration plan where you have different waves of migration and then you actually have move groups to try and get your application moved from A to  B seamlessly. A to B could be on-premise to on-premise. It could be on-premise to cloud. Et cetera.

The solution can tell me what components can I deploy, for example, into a cloud space, without having to refactor my applications since that can be quite time-consuming and costly.

Like most organizations, the one where I worked had no functional tier 2. This is because systems are so complex the vast majority of support required engineering resources. This also means that any performance ticket could wind up with just about any engineering group and often multiple groups would have to be engaged for troubleshooting. ExtraHop provides metrics and dashboards that allow IT staff to quickly triage issues and get them to the right group for remediation without having to play hot potato with multiple tickets. It makes the idea of building an effective tier 2 operations team a feasible one.

Must-have tool for advanced network/enterprise operation centers to fill in the performance gaps that host based and network performance management solutions leave. Provides the ability to execute systems and application management without being dependent on application language or APM agent qualifications.

Extensive use cases on joint workflow using ExtraHope ITOA and 3rd party APM toolsets- including real-time visualizations of business services performance mashed up and merged against L7 dependent protocols- this allows us to understand the correlation of business services degradation with performance issues with L7 protocols including HTTP, FTP and additional network services.

The biggest benefit is that our customers can assess what happens in their networks. For example, they can see why an application is slow.

We have been able to improve the mean time to resolution by several hours in some cases. We have also used it to make architectural decisions based on traffic patterns. It has been instrumental in finding problems that have been difficult to solve. 

It has greatly reduced our MTTR and root cause.