The steps below teach you how to analyze the request.log.  You start by generating traffic graphs, then cross referencing them to the request.log and rlog.jar tool output.

Steps

  1. Install perl and gnuplot on your computer

    • On Windows OS, install Cygwin.  While installing Cygwin, make sure to include perl and gnuplot during the installation on the "Select Packages" step.
    • On Mac OS(X), install brew.  After installing Brew, then open the Mac Terminal application and run brew install gnuplot to install gnuplot.
  2. Download these two files to a new folder on your computer:  

  3. Run this command against the path of your request.log:

    perl graph-request-log.pl --title "Request Log Graph" --output output.png request.log | gnuplot

    The command generates a file named output.png similar to this:

    rtaimage

    To understand the graph above you must understand the meaning of median and percentile.

    You can see in the graph above that users are not really using the system until around 7AM.  Traffic increases around 9AM then around 11:30AM. We see a spike in the number of requests and slowdown in response times overall (which can be seen in the median and 98th percentile response time markings).

    For more detailed documentation on this graphing tool, see the Readme file.

  4. Now that we know these significant times, we could cross reference those times in the request.log file using a text viewer.  

    One easy way to view large files is using the "less" command on the shell (via Cygwin on Windows or Terminal on Mac). For example, run this command "less request.log", search by typing "/2016 11:3[0-9]:" then press enter to search for 11:30AM timeframe in the file.

  5. You can also cross reference the graph to the output of the rlog.jar application that ships with AEM under opt/helpers.  Instructions can be found in the AEM docs.

Dit werk is gelicentieerd onder de Creative Commons Naamsvermelding/Niet-commercieel/Gelijk delen 3.0 Unported-licentie  De voorwaarden van Creative Commons zijn niet van toepassing op Twitter™- en Facebook-berichten.

Juridische kennisgevingen   |   Online privacybeleid