Uses of Interface
org.microproxy.FlowTracer

Packages that use FlowTracer
Package
Description
 
OpenTelemetry for MicroProxy, with no dependencies but the JDK: W3C Trace Context, B3 and Jaeger propagation (Propagators), sampling (Sampler), a SERVER span per exchange and a CLIENT span per attempt to reach the server, INTERNAL spans for tunnels and flows, and OTLP/HTTP export of traces, metrics (the proxy's StatsRegistry) and access logs, as protobuf or JSON (Telemetry).
  • Uses of FlowTracer in org.microproxy

    Fields in org.microproxy declared as FlowTracer
    Modifier and Type
    Field
    Description
    static final FlowTracer
    FlowTracer.NOOP
    Traces nothing.
    Methods in org.microproxy that return FlowTracer
    Modifier and Type
    Method
    Description
    default FlowTracer
    HttpProxyServerBootstrap.getTracer()
    Returns the tracer configured so far: NOOP without one.
    Methods in org.microproxy with parameters of type FlowTracer
    Modifier and Type
    Method
    Description
    HttpProxyServerBootstrap.withTracer(FlowTracer tracer)
    Traces the proxy's exchanges and flows with tracer (see FlowTracer): the microproxy-otel module's OpenTelemetry tracing and OTLP export, or another.
  • Uses of FlowTracer in org.microproxy.otel

    Classes in org.microproxy.otel that implement FlowTracer
    Modifier and Type
    Class
    Description
    final class 
    OpenTelemetry for the proxy, with nothing but the JDK: context propagation (W3C Trace Context, and B3 and Jaeger when configured), an X-Request-Id per request, a SERVER span per exchange (HTTP/1, HTTP/2 and HTTP/3) with a CLIENT span per attempt to reach the server, an INTERNAL span per tunnel or flow (CONNECT, SOCKS, WebSocket, CONNECT-UDP, QUIC), and the export over OTLP/HTTP, as protobuf or JSON, of those spans, of the proxy's stats as metrics, and of its access-log records as log records.