☰
Navigation :

tap.proto

Package: tap.options.gloo.solo.io

Types:

Source File: github.com/solo-io/gloo/projects/gloo/api/v1/options/tap/tap.proto

Tap

"staticConfig": .tap.options.gloo.solo.io.StaticConfig
Field Type Description
staticConfig .tap.options.gloo.solo.io.StaticConfig

StaticConfig

"outputConfig": .tap.options.gloo.solo.io.OutputConfig
Field Type Description
outputConfig .tap.options.gloo.solo.io.OutputConfig

OutputConfig

"sinks": []tap.options.gloo.solo.io.Sink
Field Type Description
sinks []tap.options.gloo.solo.io.Sink Sinks to which tap data should be output. Currently, only a single sink is supported. TODO is there a validate rule that we can use to enforce a length of 1?.

Sink

"grpcService": .tap.options.gloo.solo.io.GrpcService
Field Type Description
grpcService .tap.options.gloo.solo.io.GrpcService Write tap data out to a GRPC service .solo.io.envoy.config.core.v3.GrpcService grpc_service = 1;.

GrpcService

A tap sink over a GRPC service

"tapServer": .core.solo.io.ResourceRef
Field Type Description
tapServer .core.solo.io.ResourceRef