.. _envoy_api_file_envoy/service/trace/v2/trace_service.proto:

envoy/service/trace/v2/trace_service.proto
==========================================

.. _envoy_api_msg_service.trace.v2.StreamTracesResponse:

service.trace.v2.StreamTracesResponse
-------------------------------------

`[service.trace.v2.StreamTracesResponse proto] <https://github.com/envoyproxy/envoy/blob/v1.12.4/api/envoy/service/trace/v2/trace_service.proto#L27>`_


.. code-block:: json

  {}




.. _envoy_api_msg_service.trace.v2.StreamTracesMessage:

service.trace.v2.StreamTracesMessage
------------------------------------

`[service.trace.v2.StreamTracesMessage proto] <https://github.com/envoyproxy/envoy/blob/v1.12.4/api/envoy/service/trace/v2/trace_service.proto#L30>`_


.. code-block:: json

  {
    "identifier": "{...}",
    "spans": []
  }

.. _envoy_api_field_service.trace.v2.StreamTracesMessage.identifier:

identifier
  (:ref:`service.trace.v2.StreamTracesMessage.Identifier <envoy_api_msg_service.trace.v2.StreamTracesMessage.Identifier>`) Identifier data effectively is a structured metadata.
  As a performance optimization this will only be sent in the first message
  on the stream.
  
  
.. _envoy_api_field_service.trace.v2.StreamTracesMessage.spans:

spans
  (.opencensus.proto.trace.v1.Span) A list of Span entries
  
  
.. _envoy_api_msg_service.trace.v2.StreamTracesMessage.Identifier:

service.trace.v2.StreamTracesMessage.Identifier
-----------------------------------------------

`[service.trace.v2.StreamTracesMessage.Identifier proto] <https://github.com/envoyproxy/envoy/blob/v1.12.4/api/envoy/service/trace/v2/trace_service.proto#L31>`_


.. code-block:: json

  {
    "node": "{...}"
  }

.. _envoy_api_field_service.trace.v2.StreamTracesMessage.Identifier.node:

node
  (:ref:`core.Node <envoy_api_msg_core.Node>`, *REQUIRED*) The node sending the access log messages over the stream.