Skip to content

Optimize NO_PROXY matching for OTLP/OTAP exporters by pre-parsing rules (avoid hot-path allocations) #1711

@lalitb

Description

@lalitb

The OTLP/OTAP exporters use ProxyConfig::should_bypass()to decide whether to route a request through a proxy. Today, NO_PROXY is split/trimmed/lowercased and CIDRs are parsed on every check, causing avoidable allocations and repeated work in a hot path. Introduce a pre-parsed/compiled representation of NO_PROXY rules (exact hosts, suffix/wildcards, parsed CIDRs) and reuse it across requests, preserving current matching semantics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions