Object trending graph

The Object Trending graph enables you to visualize performance and availability for each web domain, content item, or URI for any single page of a transaction.

Use this graph to identify consistently poorly performing domains or objects. For example, if drilling down on a scatter plot indicates a specific domain or object is frequently slow, you can generate an Object Trending Graph to look at the different domains or objects over time.

**** The Object Trending graph is available ONLY to subscribers to Keynote Transaction Perspective or Application Perspective premium editions. These premium services capture all content detail during transaction measurements.

To generate an Object Trending graph:

  1. In the  > Current chart data page, select a premium edition measurement.
  2. Select Object Trending graph.
  3. Specify the graph parameters for time period, agents, and so on. Only one page of a transaction can be included. (Even if a transaction has only one page, be sure to select the page name in the Transaction Page Selection menu.)
  4. Select the component you want to use for object trending, or leave the default, Total Time.
  5. Click the Generate Graph button.

The Object Trending shows aggregated performance for the specified measurement component over time. By default, each domain serving the measured page has its own trend line on the graph.

Objects appear in the Object Trending graph if they appear at least 10 times. This limits the effect of objects that occur so infrequently as to be of no interest.

Details table

The Details Table tab displays total time for each measurement for each object displayed in the Object Trending graph.

The default graph shows the measurement details for all domains or objects represented on the current transaction page.

You can de-select one or more of the objects included and click Generate Graph Now to produce a new graph with fewer objects.

Selecting different web objects

You have several options for what to include in the Object Trending Graph:

Object data by Domain - This option aggregates the data for the selected component by web domain name. For example, measurement data from the domain news.example.com would be aggregated together with data from music.example.com and shown as one object in the Object Trending Graph and data tables.

Object data by object without parameters - This option aggregates the data for the selected component according the objects' URI up to, but not including, any query string following a question mark. For example, with this option selected, these two objects

http://www.example.com/default/css_injector_13.css?6
http://www.example.com/default/css_injector_13.css?8

would be aggregated together as one object in the Object Trending Graph and data tables.

In other words, any query string following a question mark in the URL is ignored, and objects with the same URL before a question mark are aggregated together as a single object in the Object Trending Graph and data tables despite having different query strings. This allows you to aggregate together objects that may be essentially the same in terms of web performance.

Object data by object with parameters - This option aggregates the data for the selected component according the objects' URI up to, and including, any parameters. For example, with this option selected, these two objects

http://www.example.com/default/css_injector_13.css?6
http://www.example.com/default/css_injector_13.css?8

would not be aggregated together, and would be shown as two different objects in the Object Trending Graph and data tables. Any objects having URLs with query strings following a question mark are treated as unique objects, and not aggregated together.

Trending by custom object identifier - This option is available if your transaction script contains custom objects. It will show each custom object as a separate object in the Object Trending Graph and data tables.