If your schedule run is not large, select the setting All for all types of events. For large schedule runs, do not use the All setting, because of the time and space required to transfer large amounts of log detail to your computer after a run is completed. Instead, define a special schedule for debugging tests with the log levels set to All. Limit this schedule to a single test (or a small number of tests) and to a small number of user groups or loop iterations. After you are satisfied that a test is performing correctly, you can move it to a schedule that emulates a realistic workload.
To view the Event Log information:
The first column has an arrow to indicate the page that is currently displayed in the other Protocol Data view windows: Request, Response Headers, Response Content, and Browser.
| Symbol | Meaning |
|---|---|
| Green check | All requests for the page are successful and that there are no warnings. |
| Red X | The page contains requests with failed verdicts or unexpected response codes. Typically, failed verdicts are verification point failures. Unexpected response codes are codes outside the 200 and 300 range that were not recorded as such or that are not represented in associated verification points. |
| Yellow warning symbol | The page contains messages but no failure verdicts or unexpected response codes. |
