Powerful Diagnostics
Record detailed Flash & Silverlight interactions like mouse-clicks, hover-overs, text entry and system-key navigation such as tab, enter or function keys using our new Screen Sensing Technology™.
When you play your script, the Flash or Silverlight application is actually exercised, not just downloaded. KITE 3.0 captures all network activity generated as the Flash or Silverlight application responds to the scripted user input allowing you to quickly determine, which interaction contributes to a performance slowdown.
Here we show the MiniCooper site, which is built 100% in Flash. We navigate to miniusa.com, look for a dealer within a certain zip-code area and all dealer locations are displayed. The script shows each step of the Flash interaction.
If your pages contain data from a variety of sources, e.g., CDN-served page elements like ads or images, you want to see the response time for your content separately from the third-party content.
The new Filters and Virtual Pages features let you focus on the page elements that matter and eliminate the ones that do not.
Filters define what makes it through to a Virtual Page:
Any number of Virtual Pages can be constructed from a single physical page:
Each of these Virtual Pages is then sent to your MyKeynote portal as a separate page in your transaction. This way you can use MyKeynote’s powerful alarms, trending graphs and reporting tools on just the data that matter most to you.
You can filter by defining one or more Match Page Elements statements. These statements can contain simple strings such as the domain portion of a URL (http://www.mysite.com) or highly flexible regular expression formulas. The types of filtering statements are listed in the below screenshot:
Create Deep Diagnostic ProbesTo capture data needed for monitoring and troubleshooting we have made it easy for you to create deep diagnostic probes with the Add Automated Custom Components feature. You can add calculated or custom-extracted data to your monitoring results easily.
We will show you below two examples of how to capture such data.
Example 1: Capture Browser Thinking Time
When diagnosing issues, you need to know how much time elapses between a large JavaScript file being downloaded and the browser requesting an object called for by that JavaScript code. Define an automated custom component that is set to the difference in miliseconds between the end of the JavaScript download and the start of the object called for.
Here is an example of a JavaScript file (js), a delay while the browser interprets the js file and then the next element being requested after the delay:
The “delta between elements” component can bring back that figure from every monitoring transaction and alert you if changes to the JavaScript have significantly impacted timing.
Example 2: Capture server name along with measurements
If you have a large server farm finding a server-specific problem can be like finding a needle in a haystack. If you are already populating http headers with custom data indicating the server instance servicing the session, you can now capture that server name right along with the measurement. So when you get an alarm you know instantly, which server caused it. All you need to do is define an automated custom component that tells KITE and the TxP agent what to capture as each measurement is recorded:
What's New?
Getting to Know KITE 3.0
Learn what’s new in KITE 3.0 in this five-minute video hosted by KITE product manager, Dave Karow.
Click Here 
Web Performance Community
Webcast
