Radware Alteon Body Capture Configuration

Overview

The Radware Alteon Body Capture Configuration describes how to configure Radware Alteon load balancers to capture and transmit API transaction body data. This capability is crucial for platforms requiring deep inspection or logging of API traffic. For v1 of the platform, this configuration is provided as documentation only and is not actively maintained within this directory, unlike configurations for HAProxy and Nginx (source: deploy/lb-connectors/radware/README.md).

Operators are expected to consult the referenced RFC section and adapt the provided AppShape++ or syslog configurations to their specific environment (source: deploy/lb-connectors/radware/README.md).

This configuration enables the Radware Alteon to:

• Capture L7 http: and L4 slb: log lines.
• Map these log lines to "BB #12 envelope fields".
• Post the "BB #12 envelope" to a relay VM for each HTTP transaction (source: deploy/lb-connectors/radware/README.md).

How it Works

Radware Alteon body capture operates through two primary mechanisms: syslog configuration and AppShape++ scripting (source: deploy/lb-connectors/radware/README.md).

1. Syslog Configuration:

   • The Alteon can be configured via its web UI or CLI to capture specific log lines (source: deploy/lb-connectors/radware/README.md).
   • It captures dual-path log lines, specifically L7 http: for HTTP-layer information and L4 slb: for SLB-layer information (source: deploy/lb-connectors/radware/README.md).
   • These captured log lines are then formatted and their fields are mapped to a "BB #12 envelope fields" structure (source: deploy/lb-connectors/radware/README.md).

2. AppShape++ Body Capture Script:

   • An AppShape++ (JavaScript) script is deployed on the Alteon (source: deploy/lb-connectors/radware/README.md).
   • This script is responsible for capturing the HTTP body during an HTTP transaction (source: deploy/lb-connectors/radware/README.md).
   • Upon capturing, the script constructs a "BB #12 envelope" containing the body data and other relevant transaction details (source: deploy/lb-connectors/radware/README.md).
   • The script then POSTs this "BB #12 envelope" to a designated relay VM for further processing (source: deploy/lb-connectors/radware/README.md).
   • The AppShape++ script requires binding to real (server group) and virt (virtual service) configurations on the Alteon (source: deploy/lb-connectors/radware/README.md).

Configuration Details

The comprehensive configuration details for Radware Alteon body capture are documented externally (source: deploy/lb-connectors/radware/README.md).

Specifically, the following aspects are covered in the referenced RFC:

• Syslog Configuration: Instructions for configuring syslog via the Alteon web UI or CLI (path: /cfg/slb/perf/log) (source: deploy/lb-connectors/radware/README.md).
• Syslog Format and Field Mapping: The recommended syslog format and how to map fields from L7 http: and L4 slb: log lines to "BB #12 envelope fields" (source: deploy/lb-connectors/radware/README.md).
• AppShape++ Script: Details on the JavaScript body-capture script that POSTs the "BB #12 envelope" to the relay VM (source: deploy/lb-connectors/radware/README.md).
• Binding: How to bind the AppShape++ script to real (server group) and virt (virtual service) configurations (source: deploy/lb-connectors/radware/README.md).

The source does not provide a direct configuration table with specific parameters, types, defaults, or requirements. Operators should refer to the external RFC for these details.

API / CLI / Endpoint Reference

CLI Paths

• Syslog Configuration: /cfg/slb/perf/log (source: deploy/lb-connectors/radware/README.md)
  • Description: Path within the Radware Alteon CLI for configuring performance logging, including syslog settings.

External Endpoints

• Relay VM Endpoint: The AppShape++ script POSTs the "BB #12 envelope" to a relay VM (source: deploy/lb-connectors/radware/README.md).
  • Description: The specific endpoint path on the relay VM is not defined in the source.
  • Inputs: "BB #12 envelope" (source: deploy/lb-connectors/radware/README.md).
  • Outputs: Not specified in the source.
  • Error Responses: Not specified in the source.

Troubleshooting

Known Limitations and Prerequisites

• Alteon Version Requirement: AppShape++ body capture functionality requires Radware Alteon version 30.x or newer (source: deploy/lb-connectors/radware/README.md).
• License Requirement: An "AppShape++ Advanced" license is mandatory for utilizing AppShape++ body capture (source: deploy/lb-connectors/radware/README.md).

The source does not specify other error conditions, status codes, retries, or timeouts.

Contributions

Contributions of tested Radware Alteon AppShape++ scripts or syslog configurations are welcome. To contribute, open a Pull Request (PR) that includes:

• The .js script file for AppShape++.
• An updated version of this README, including installation steps.

Alternatively, an issue can be opened describing the environment and the tested configuration (source: deploy/lb-connectors/radware/README.md). Refer to docs/lld/contribution-guidelines.md for general contribution guidelines (source: deploy/lb-connectors/radware/README.md).

See Also

• docs/rfc/lb-syslog-discovery.md §2.6 — "Radware Alteon (BB #10)" (source: deploy/lb-connectors/radware/README.md)
• docs/backlog.md (for decision D1 regarding v1 maintenance status) (source: deploy/lb-connectors/radware/README.md)
• docs/lld/contribution-guidelines.md (source: deploy/lb-connectors/radware/README.md)
• HAProxy and Nginx body-capture scripts (mentioned as actively maintained alternatives in v1) (source: deploy/lb-connectors/radware/README.md)

---

All SOAP-to-REST docs