Lookout Product Documentation

Find answers about using and optimizing Lookout products.

Configure HAR Logging

HAR logging can be configured for Cloud environment types.

HAR logging enables generation of HTTP Archive (HAR) logs, which show information regarding network requests generated in a browser when an issue occurs. HAR logs can provide valuable information such as how long an object takes to be requested, the time required to connect to the server, and the time taken to transfer items from the server to the browser, as well as actions by privileged users. A HAR log can help you detect problems such as excessively long load times, no loading activity, or no caching taking place.

Generated HAR logs are in JSON format.

IMPORTANT

HAR logging is done in memory for security purposes. Sensitive information such as passwords are typically included, so use HAR logging with care.

  1. Click the Live Debugging Enable toggle.
  2. Enter the following information.
    FieldDescription
    Select Node(s)From the list, select the nodes to be included in the HAR log.
    Log File PrefixEnter a log file prefix to help identify the HAR file.
    Log File PasswordEnter a password for accessing the HAR log. This password is used to encrypt the zip file and will be required for extracting the file.
    Log File Max SizeEnter the maximum file size for the HAR log or accept the default size of 10MB.
  3. Click Save.
  4. Click Start HAR Log.
    The button name will change to Stop HAR Log and the icon to a red circle containing a white square.
  5. Run tests.
  6. Click Stop HAR Log again to stop the log.
    If you do not stop the log, it will run until the specified Log File Max Size is reached.

    Generated HAR logs are listed at the bottom of the Debugging page. The list includes the following information about each HAR log:

    FieldDescription
    Node NameThe name(s) of the node(s) included in the log.
    Log FileThe system-generated name of the HAR log file. (*.har)
    Start TimeThe day and time that HAR logging starts.
    End TimeThe day and time that HAR logging ends.
    StatusThe progress of the HAR log (for example, in progress or completed).
    PasswordThe debugging password you created in the Log File Password field.
    ActionAny actions indicated by the logging process.

    Because of the large file sizes that are often generated, HAR logging could have an impact on system performance. HAR logging should be done only for short periods of time when an activity of interest is in progress. We recommend working with Support when running HAR logs..