We can further amend the search to offer granular information on average response times by the type of action being performed. This might pinpoint some actions that are less responsive than other actions. For example, we might want to ensure that the checkout page remains at an optimal load time. For the following search to work, you must complete the Defining field extractions recipe in Chapter 1, Play Time – Getting Data In, to extract the response field:
sourcetype=access_combined uri_path=* | timechart span=6h avg(response) by uri_path | foreach * [eval <<FIELD>>=round('<<FIELD>>'/1000,2)]
We are now searching for web page events, and then we will calculate the average time by page (uri_field ...
