Skip to content

Update HTTP payload-enrichment configuration #2986

Description

@marctc

HTTP payload-enrichment rules can conditionally include, exclude, or obfuscate data according to response status codes and JSON paths. Individual rules can also define their own replacement string.

Fields to document

  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.equals
  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.not_equals
  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.greater_than
  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.greater_equals
  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.less_than
  • ebpf.payload_extraction.http.enrichment.rules[].match.response_status_code.less_equals
  • ebpf.payload_extraction.http.enrichment.rules[].match.obfuscation_json_paths
  • ebpf.payload_extraction.http.enrichment.rules[].obfuscation_string

Document how multiple status-code comparisons are combined, when JSON-path matching applies, and how a rule-level obfuscation string interacts with the policy-level value. Include focused YAML examples.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions