package envoy.service.tap.v3

Get desktop application:
View/edit binary Protocol Buffers messages

[#not-implemented-hide:] A tap service to receive incoming taps. Envoy will call StreamTaps to deliver captured taps to the server

• rpc StreamTaps (stream StreamTapsRequest, StreamTapsResponse)

  tap.proto:26

  Envoy will connect and send StreamTapsRequest messages forever. It does not expect any response to be sent as nothing would be done in the case of failure. The server should disconnect if it expects Envoy to reconnect.

  message StreamTapsRequest

  tap.proto:32

  [#not-implemented-hide:] Stream message for the Tap API. Envoy will open a stream to the server and stream taps without ever expecting a response.

  • optional StreamTapsRequest.Identifier identifier = 1

    Identifier data effectively is a structured metadata. As a performance optimization this will only be sent in the first message on the stream.

  • uint64 trace_id = 2

    The trace id. this can be used to merge together a streaming trace. Note that the trace_id is not guaranteed to be spatially or temporally unique.

  • optional data.tap.v3.TraceWrapper trace = 3

    The trace data.

  message StreamTapsResponse

  tap.proto:61

  [#not-implemented-hide:]

  (message has no fields)

Used in: StreamTapsRequest

• optional config.core.v3.Node node = 1

  The node sending taps over the stream.

• string tap_id = 2

  The opaque identifier that was set in the :ref:`output config <envoy_v3_api_field_config.tap.v3.StreamingGrpcSink.tap_id>`.