Symptoms

The stats for request-adapt and response-adapt profile aggregate all dynamic contexts into a single row, which can hinder debug or analysis of the use of dynamic adaptation contexts. The interface between the parent virtual server with those profiles, and the internal virtual server, cannot be packet-captured, which can increase the difficulty with debugging.

Impact

Difficult to debug and analyze dynamic context behavior. Difficult to diagnose IVS related issues due to lack of visibility of the internal non-TCP interface.

Conditions

Adaption profile request-adapt or response-adapt, and an internal virtual server.

Workaround

None.

Fix Information

Statistics for request-adapt and response-adapt profiles now use separate rows for dynamic contexts, allowing greater visibility into usage of each dynamic context by name. Log messages for request-adapt and response-adapt provide key flow information. Additional messages provide information regarding dynamic contexts. Log messages for an internal virtual server provide transaction information to increase visibility on the software interface between the ADAPT filter and an internal virtual server.

Behavior Change

Statistics for request-adapt and response-adapt profiles use separate rows for dynamic contexts by name (previously they were all aggregated into the single stats row for the profile). Log messages for request-adapt and response-adapt provide key flow information, and additional messages provide more information regarding dynamic contexts. The log level is set by the existing DB variable log.adapt.level. More log messages for an internal virtual server provide transaction information to increase visibility on the internal IVS interface between the ADAPT filter and an IVS. The log level is set by the existing DB variable log.ivs.level.