package envoy.service.event_reporting.v3

Get desktop application:
View/edit binary Protocol Buffers messages

[#not-implemented-hide:] Service for streaming different types of events from Envoy to a server. The examples of such events may be health check or outlier detection events.

• rpc StreamEvents (stream StreamEventsRequest, stream StreamEventsResponse)

  event_reporting_service.proto:28

  Envoy will connect and send StreamEventsRequest messages forever. The management server may send StreamEventsResponse to configure event stream. See below. This API is designed for high throughput with the expectation that it might be lossy.

  message StreamEventsRequest

  event_reporting_service.proto:34

  [#not-implemented-hide:] An events envoy sends to the management server.

  • optional StreamEventsRequest.Identifier identifier = 1

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

  • repeated google.protobuf.Any events = 2

    Batch of events. When the stream is already active, it will be the events occurred since the last message had been sent. If the server receives unknown event type, it should silently ignore it. The following events are supported: * :ref:`HealthCheckEvent <envoy_v3_api_msg_data.core.v3.HealthCheckEvent>` * :ref:`OutlierDetectionEvent <envoy_v3_api_msg_data.cluster.v3.OutlierDetectionEvent>`

  message StreamEventsResponse

  event_reporting_service.proto:66

  [#not-implemented-hide:] The management server may send envoy a StreamEventsResponse to tell which events the server is interested in. In future, with aggregated event reporting service, this message will contain, for example, clusters the envoy should send events for, or event types the server wants to process.

  (message has no fields)

Used in: StreamEventsRequest

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

  The node sending the event messages over the stream.