Get desktop application:
View/edit binary Protocol Buffers messages
This filter will inspect and get attributes from A2A traffic. [#next-free-field: 6]
Configures how the filter handles non-A2A traffic.
Maximum size of the request body to buffer for JSON-RPC validation. If the request body exceeds this size, the request is rejected with ``413 Payload Too Large``. This limit applies to both ``REJECT`` and ``PASS_THROUGH`` modes to prevent unbounded buffering. It defaults to 8KB (8192 bytes) and the maximum allowed value is 10MB (10485760 bytes). Setting it to 0 would disable the limit. It is not recommended to do so in production.
Customized configuration for A2A parser.
Where to store parsed A2A message attributes. Controls whether attributes are written to dynamic metadata, filter state, or both. Default is no storage.
Where to store parsed A2A message attributes.
Used in:
Default behavior: no storage.
Store message attributes in dynamic metadata only.
Store message attributes in filter state only.
Store message attributes in both dynamic metadata and filter state.
Traffic handling mode for non-A2A traffic.
Used in:
Proxies the HTTP request and response without A2A spec check.
Reject requests that are not following A2A spec.
Used in:
The group/category name to assign to this method (e.g., "tasks", "message"). If provided, this overrides any built-in classification for the method. This will be emitted to dynamic metadata under the key specified by ``group_metadata_key``.
List of attributes to extract for this method, specified by their JSON paths (e.g., "params.name").
Used in:
Method-specific overrides for grouping and attribute extraction. If a method is not specified in method_configs, or if 'group' is empty in its config, its group will be determined by built-in classification based on method prefix (e.g., "message" for "message/send") and default extraction rules will be applied for that method.
Attributes that should always be extracted regardless of the method. Specified by their JSON paths (e.g., "params.id").
The dynamic metadata key under which the method's group name will be stored (e.g., "a2a_group"). If this key is empty, group information will not be added to dynamic metadata.