Extended Error Logging

by Community Manager on 07-06-2011 03:21 PM - last edited on 10-18-2011 12:14 PM by Community Manager

For additonal logging information, an "Extended Error" option can be set for the Transport level in the Composition Editor's Composition Properties, Play Settings tab, Logging section.

 

Setting Extended Error at this level affects logging for all messages in the test composition. This option is useful for load test or large functional tests where the detailed Verbose logging of successful messages is not necessary.

Composition Editor, logging properties

Setting Extended Error Logging at the Transport Level

  1. Open the composition in the Composition Editor, and then click the Properties tab on the lower left.
  2. Click the Composition node in the Properties list. The Composition Properties, General tab settings appear in the tabs on the right.

    1. Check Edit Advanced Settings.
    2. Optionally, uncheck Save Clip Element Details, Save Composition Element Details, or both, depending on the type of test.

The resulting information will be shown in the Result Details and Event Log widgets unless the Save Clip Element Details and Save Composition Element Details checkboxes are unchecked, in which case only only the Event Log widget will display extended information. Typically, clip element and composition element details are unchecked for large load tests.

  1. With Edit Advanced Settings checked, scroll down to reveal the Transport logging setting in the Logging section on the right.
  2. Click the Transport drop-down and selected Extended Error.

    1. Optionally, set an Event Count limit.

The Event Count Limit is used whenever Extended Error is enabled in a large load test. This setting limits the total number of events (NOT just error events, but all events) that can be logged into the Event Log.

For example, an integer between 1,000 to 20,000 is a reasonable range. An upper limit of 20,000 will prevent too many error events if the test goes awry and starts generating billions of errors, while a lower limit of 1,000 will capture enough data to be helpful.

When Extended Error is set for Transport logging, the message(s) sent and the message(s) received will be captured if the message has an error or does not pass validations that are set. For messages that have no error, the effect will be to not log anything.

Note: The Extended Error setting currently only has meaning at the “Transport” level and is the same as "Error" at all other levels.

 

The example screenshot on the right shows detail from the Event Log widget when “Error” level is set:

Event Logs widget detail, Error level set

Here is the same test with “Extended Error” set:

Event Logs widget detail, Error level set