1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
// Copyright 2023 The RocketMQ Rust Authors
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
use Any;
use Arc;
use CheetahString;
use crateAccessChannel;
/// The type of tracing operation being performed.
///
/// This enum distinguishes between producer-side and consumer-side tracing,
/// allowing the trace dispatcher to handle different types of message flow tracking.
/// A dispatcher that manages the collection and transmission of message tracing data.
///
/// The `TraceDispatcher` trait defines the interface for components that collect
/// message tracing information and send it to a trace storage backend. It supports
/// both producer and consumer side tracing, enabling end-to-end message flow tracking
/// in RocketMQ applications.
///
/// # Purpose
///
/// Message tracing provides visibility into:
/// - Message production: send time, broker, topic, tags, keys
/// - Message consumption: consume time, status, retry times
/// - Message routing: which brokers and queues handled the message
///
/// # Implementation Notes
///
/// Implementations must be thread-safe (`Send + Sync`) as they may be accessed
/// concurrently from multiple producer or consumer threads. The dispatcher typically
/// batches trace data and sends it asynchronously to minimize performance impact.
///
/// # Lifecycle
///
/// 1. Create and configure the dispatcher
/// 2. Call [`start`](TraceDispatcher::start) to initialize and connect
/// 3. Call [`append`](TraceDispatcher::append) to add trace contexts
/// 4. Call [`flush`](TraceDispatcher::flush) periodically or before shutdown
/// 5. Explicitly shut down the dispatcher for graceful cleanup. Async
/// implementations should expose and document a non-blocking async shutdown
/// entry point for callers running on a Tokio worker.
/// Type alias for an atomically reference-counted trace dispatcher.
///
/// This is the standard way to share a [`TraceDispatcher`] implementation across multiple
/// threads or components. The `Arc` provides thread-safe reference counting.
///
/// # Thread Safety
///
/// `ArcTraceDispatcher` is both `Send` and `Sync`, allowing it to be safely shared
/// across thread boundaries and accessed concurrently from multiple threads.
///
/// # Examples
///
/// ```ignore
/// use std::sync::Arc;
/// use crate::trace::trace_dispatcher::{TraceDispatcher, ArcTraceDispatcher};
/// use crate::trace::async_trace_dispatcher::AsyncTraceDispatcher;
///
/// // Create a dispatcher
/// let dispatcher = AsyncTraceDispatcher::new("ProducerGroup", Type::Produce, "TraceTopic", None);
/// let arc_dispatcher: ArcTraceDispatcher = Arc::new(dispatcher);
///
/// // Share across threads
/// let dispatcher_clone = arc_dispatcher.clone();
/// ```
pub type ArcTraceDispatcher = ;