anchor.diff:  
   ## <a id="within-cf"></a> Experiment 2: View Request Time in Access Logs
   
  +In <%= vars.app_runtime_abbr %>, delays can occur within Gorouter, within the app, or within the network between the two.
   If you suspect that you are experiencing latency, the most important logs are the access logs. The
   `cf logs` command streams log messages from Gorouter as well as from apps. This section describes
   how to find and understand the access log timestamps.
  
positive.code:       </tr>
        <tr>
          <td width="25%">The output shows latency within <code>gorouter_time</code>.</td>
          <td>Gorouter, or the network between the end user + gorouter is causing the latency</td>
          <td>Continue with the rest of the experiments to try to narrow down which component is
              causing latency.</td>
        </tr>
        <tr>
          <td width="25%">The output shows latency within <code>response_time</code> but not in
              <code>gorouter_time</code>.</td>
          <td>The network between gorouter and the app, or the app itself is causing latency.</td>
          <td>Jump to experiment 5, and continue with the rest of the experiments to try to narrow
              down which component is causing latency.</td>
        </tr>
        <tr>
          <td>The output does not show latency within <code>response_time</code>.</td>
          <td>A component before Gorouter is causing latency to the request before it reaches the
              gorouter initially.</td>
          <td>Continue with the rest of the experiments to try to narrow down which component is
              causing latency.</td>
        </tr>
  
negative.code:     <td>A component before Gorouter is causing latency.</td>
      <td>Look at your load balancer logs and logs for any other components that exist between the
          end client and Gorouter. Additionally, run these experiments with clients in different networks
          to help isolate where issues occur.</td>
    </tr>
  </table>
  
  