public static enum OutputSink.Format extends Enum<OutputSink.Format> implements com.google.protobuf.ProtocolMessageEnum
Output format. All output is in the form of one or more :ref:`TraceWrapper <envoy_api_msg_data.tap.v3.TraceWrapper>` messages. This enumeration indicates how those messages are written. Note that not all sinks support all output formats. See individual sink documentation for more information.Protobuf enum
envoy.config.tap.v4alpha.OutputSink.Format| Enum Constant and Description |
|---|
JSON_BODY_AS_BYTES
Each message will be written as JSON.
|
JSON_BODY_AS_STRING
Each message will be written as JSON.
|
PROTO_BINARY
Binary proto format.
|
PROTO_BINARY_LENGTH_DELIMITED
Messages are written as a sequence tuples, where each tuple is the message length encoded
as a `protobuf 32-bit varint
<https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.io.coded_stream>`_
followed by the binary message.
|
PROTO_TEXT
Text proto format.
|
UNRECOGNIZED |
| Modifier and Type | Field and Description |
|---|---|
static int |
JSON_BODY_AS_BYTES_VALUE
Each message will be written as JSON.
|
static int |
JSON_BODY_AS_STRING_VALUE
Each message will be written as JSON.
|
static int |
PROTO_BINARY_LENGTH_DELIMITED_VALUE
Messages are written as a sequence tuples, where each tuple is the message length encoded
as a `protobuf 32-bit varint
<https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.io.coded_stream>`_
followed by the binary message.
|
static int |
PROTO_BINARY_VALUE
Binary proto format.
|
static int |
PROTO_TEXT_VALUE
Text proto format.
|
| Modifier and Type | Method and Description |
|---|---|
static OutputSink.Format |
forNumber(int value) |
static com.google.protobuf.Descriptors.EnumDescriptor |
getDescriptor() |
com.google.protobuf.Descriptors.EnumDescriptor |
getDescriptorForType() |
int |
getNumber() |
com.google.protobuf.Descriptors.EnumValueDescriptor |
getValueDescriptor() |
static com.google.protobuf.Internal.EnumLiteMap<OutputSink.Format> |
internalGetValueMap() |
static OutputSink.Format |
valueOf(com.google.protobuf.Descriptors.EnumValueDescriptor desc) |
static OutputSink.Format |
valueOf(int value)
Deprecated.
Use
forNumber(int) instead. |
static OutputSink.Format |
valueOf(String name)
Returns the enum constant of this type with the specified name.
|
static OutputSink.Format[] |
values()
Returns an array containing the constants of this enum type, in
the order they are declared.
|
public static final OutputSink.Format JSON_BODY_AS_BYTES
Each message will be written as JSON. Any :ref:`body <envoy_api_msg_data.tap.v3.Body>` data will be present in the :ref:`as_bytes <envoy_api_field_data.tap.v3.Body.as_bytes>` field. This means that body data will be base64 encoded as per the `proto3 JSON mappings <https://developers.google.com/protocol-buffers/docs/proto3#json>`_.
JSON_BODY_AS_BYTES = 0;public static final OutputSink.Format JSON_BODY_AS_STRING
Each message will be written as JSON. Any :ref:`body <envoy_api_msg_data.tap.v3.Body>` data will be present in the :ref:`as_string <envoy_api_field_data.tap.v3.Body.as_string>` field. This means that body data will be string encoded as per the `proto3 JSON mappings <https://developers.google.com/protocol-buffers/docs/proto3#json>`_. This format type is useful when it is known that that body is human readable (e.g., JSON over HTTP) and the user wishes to view it directly without being forced to base64 decode the body.
JSON_BODY_AS_STRING = 1;public static final OutputSink.Format PROTO_BINARY
Binary proto format. Note that binary proto is not self-delimiting. If a sink writes multiple binary messages without any length information the data stream will not be useful. However, for certain sinks that are self-delimiting (e.g., one message per file) this output format makes consumption simpler.
PROTO_BINARY = 2;public static final OutputSink.Format PROTO_BINARY_LENGTH_DELIMITED
Messages are written as a sequence tuples, where each tuple is the message length encoded as a `protobuf 32-bit varint <https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.io.coded_stream>`_ followed by the binary message. The messages can be read back using the language specific protobuf coded stream implementation to obtain the message length and the message.
PROTO_BINARY_LENGTH_DELIMITED = 3;public static final OutputSink.Format PROTO_TEXT
Text proto format.
PROTO_TEXT = 4;public static final OutputSink.Format UNRECOGNIZED
public static final int JSON_BODY_AS_BYTES_VALUE
Each message will be written as JSON. Any :ref:`body <envoy_api_msg_data.tap.v3.Body>` data will be present in the :ref:`as_bytes <envoy_api_field_data.tap.v3.Body.as_bytes>` field. This means that body data will be base64 encoded as per the `proto3 JSON mappings <https://developers.google.com/protocol-buffers/docs/proto3#json>`_.
JSON_BODY_AS_BYTES = 0;public static final int JSON_BODY_AS_STRING_VALUE
Each message will be written as JSON. Any :ref:`body <envoy_api_msg_data.tap.v3.Body>` data will be present in the :ref:`as_string <envoy_api_field_data.tap.v3.Body.as_string>` field. This means that body data will be string encoded as per the `proto3 JSON mappings <https://developers.google.com/protocol-buffers/docs/proto3#json>`_. This format type is useful when it is known that that body is human readable (e.g., JSON over HTTP) and the user wishes to view it directly without being forced to base64 decode the body.
JSON_BODY_AS_STRING = 1;public static final int PROTO_BINARY_VALUE
Binary proto format. Note that binary proto is not self-delimiting. If a sink writes multiple binary messages without any length information the data stream will not be useful. However, for certain sinks that are self-delimiting (e.g., one message per file) this output format makes consumption simpler.
PROTO_BINARY = 2;public static final int PROTO_BINARY_LENGTH_DELIMITED_VALUE
Messages are written as a sequence tuples, where each tuple is the message length encoded as a `protobuf 32-bit varint <https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.io.coded_stream>`_ followed by the binary message. The messages can be read back using the language specific protobuf coded stream implementation to obtain the message length and the message.
PROTO_BINARY_LENGTH_DELIMITED = 3;public static final int PROTO_TEXT_VALUE
Text proto format.
PROTO_TEXT = 4;public static OutputSink.Format[] values()
for (OutputSink.Format c : OutputSink.Format.values()) System.out.println(c);
public static OutputSink.Format valueOf(String name)
name - the name of the enum constant to be returned.IllegalArgumentException - if this enum type has no constant with the specified nameNullPointerException - if the argument is nullpublic final int getNumber()
getNumber in interface com.google.protobuf.Internal.EnumLitegetNumber in interface com.google.protobuf.ProtocolMessageEnum@Deprecated public static OutputSink.Format valueOf(int value)
forNumber(int) instead.public static OutputSink.Format forNumber(int value)
public static com.google.protobuf.Internal.EnumLiteMap<OutputSink.Format> internalGetValueMap()
public final com.google.protobuf.Descriptors.EnumValueDescriptor getValueDescriptor()
getValueDescriptor in interface com.google.protobuf.ProtocolMessageEnumpublic final com.google.protobuf.Descriptors.EnumDescriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.ProtocolMessageEnumpublic static final com.google.protobuf.Descriptors.EnumDescriptor getDescriptor()
public static OutputSink.Format valueOf(com.google.protobuf.Descriptors.EnumValueDescriptor desc)
Copyright © 2018–2021 The Envoy Project. All rights reserved.