package solace.messaging.proto.broker.trace.move.v1

Get desktop application:
View/edit binary Protocol Buffers messages

The presence of this message implies the reason for the span is that a message exceeded the maximum number of redeliveries.

Used in: SpanData

(message has no fields)

The presence of this message implies the reason for the span is that a consuming client settled the message with an outcome of "rejected".

Used in: SpanData

(message has no fields)

Messages with the following topic contain a message matching this specification: _telemetry/broker/trace/move/v1[/additional/topic/levels] Note that the topic allows for additional topic levels to be added in the future. Receiving clients must not assume there are no additional topic levels. This message describes telemetry data that a Solace PubSub+ broker captures as a result of moving a message from one queue to another; for example, moving a message to a dead message queue if TTL expires. Fields with names that end in "time_unix_nano" are 64-bit timestamps, in nanoseconds, since midnight, Jan. 1, 1970 UTC.

• bytes trace_id = 1

  16-byte globally unique trace ID. Any two spans with the same trace ID are part of the same trace.

• bytes span_id = 2

  8-byte span ID, unique within the scope of a trace.

• optional bytes parent_span_id = 3

  If not present, this is a root span. If present, this is an 8-byte span ID of the parent span.

• sfixed64 start_time_unix_nano = 4

  The start and end timestamps of the receive span. The start of the span is when Guaranteed Messaging processing begins in the broker.

• sfixed64 end_time_unix_nano = 5

• oneof source

  The name of the queue or topic endpoint the message is being moved from.

  • string source_queue_name = 6

  • string source_topic_endpoint_name = 7

• oneof destination

  The destination queue or topic endpoint the message is being moved to.

  • string destination_queue_name = 8

  • string destination_topic_endpoint_name = 9

• oneof type_info

  The nested "info" message below provides the following information: * The reason for the message being moved. * Any additional information associated with that particular reason. Currently, the defined "info" messages contain no information. An enum could have been used to express this instead. The "info" message technique was chosen to allow for information related specifically to each scenario to be easily added in the future.

  • MaxRedeliveriesInfo max_redeliveries_info = 10

  • TtlExpiredInfo ttl_expired_info = 11

  • RejectedOutcomeInfo rejected_outcome_info = 12

• string router_name = 13

  The router-name of the broker generating this message at the time the message was generated.

• optional string message_vpn_name = 14

  The broker's message-vpn name. This field may be removed in the future without a major version change since the field is specified as optional. Rather than rely on this field, receiving clients should obtain the VPN by using an SMF API to extract the VPN_NAME_IN_USE from the API's Session object. The message_vpn_name of all messages received from via an SMF API's session will match the session's VPN_NAME_IN_USE.

• string solos_version = 15

  The SolOS version of the broker generating the message. All elements of egress_spans will always have been created by the same broker version.

• optional bytes replication_group_message_id = 16

• optional uint32 source_partition_number = 17

  Partition number of queue the message is being moved from, if the associated queue is a partitioned queue

• optional uint32 destination_partition_number = 18

  Partition number of the destination DMQ the message is being moved to, if the associated queue is a partitioned queue

The presence of this message implies the reason for the span is that the message's TTL has expired.

Used in: SpanData

(message has no fields)