Unable to see events/steps in inspection view for Virtual Service.

Products

• CA Application Test
• CA Continuous Application Insight (PathFinder)

Issue/Introduction

Summary:  

 - When the virtual services have more number of steps and are do not display the events or steps in inspection view, what properties can be set in local.properties file for that particular VSE.

 

Environment

Release: DevTest 10.x
Component:

Cause

The value for the request event buffer size is low for the number of events being generated.

Resolution

Instructions: 

- These two properties are defined with their default values in lisa.properties file but should never be modified in lisa.properties.

- These two properties should be overridden in local.properties for the concerned VSE.

lisa.vse.match.event.buffer.size=200

lisa.vse.request.event.set.buffer.size=200

- Details of two properties:

lisa.vse.match.event.buffer.size

This property sets the number of events for each VS model to define how many matching related events VSE buffers. The property sets the number of events for each VS model. For example, if two VS models are deployed with the default event buffer size of 100, then 200 events are buffered. These events are the source for the Match tab of the VS model inspection page in the VSE dashboard.

Default: 100

lisa.vse.request.event.set.buffer.size

This property defines the number of inbound VSE requests for which a full set of DevTest events is buffered. The property sets the number of events for each VS model. For example, if two VS models are deployed with the default request buffer size (5), ten sets of events (grouped by inbound request) are buffered. These sets of events are the source for the Events tab of the VS model inspection page in the VSE dashboard.

For performance reasons, VSE holds 50 events for processing. This limit can result in the removal of events from the processing queue and the absence of events in the Inspection View. To prevent the truncation of events, you can increase the size of the event processing queue. However, this action can increase memory usage and can reduce performance.

The '(unknown)' steps can happen for three reasons:

1. The value for the request event buffer size is low for the number of events being generated.

2. The number of events being generated depends on the logging level set to the VSE. If set to the DEBUG it will generate too many events and the value of 200 might be insufficient.

3. An additional step was added to the VSM and is set to "Quiet".