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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
//! Scenario configuration: YAML deserialization and validation.
use HashMap;
use Deserialize;
use crateEncoderConfig;
use crate;
use crateSinkConfig;
/// Gap window configuration — a recurring silent period within a scenario.
///
/// During a gap the scheduler emits no events. The gap repeats on a fixed
/// cycle defined by `every`, and each instance lasts for `for`.
/// Burst window configuration — a recurring high-rate period within a scenario.
///
/// During a burst the event rate is multiplied by `multiplier`. The burst
/// repeats on a fixed cycle defined by `every`, and each instance lasts for `for`.
///
/// If a gap and burst overlap in time, the gap takes priority and no events
/// are emitted.
/// Full configuration for a single scenario run.
///
/// Deserialized from a YAML scenario file. CLI flags can override any field.
///
/// # Example YAML
///
/// ```yaml
/// name: interface_oper_state
/// rate: 1000
/// duration: 30s
/// generator:
/// type: sine
/// amplitude: 5.0
/// period_secs: 30
/// offset: 10.0
/// gaps:
/// every: 2m
/// for: 20s
/// labels:
/// hostname: t0-a1
/// zone: eu1
/// encoder:
/// type: prometheus_text
/// sink:
/// type: stdout
/// ```
/// A single entry in a multi-scenario configuration.
///
/// The `signal_type` tag selects whether this entry is a metrics or logs scenario.
/// Deserialized from a YAML multi-scenario file where each element of the
/// `scenarios` list carries a `signal_type: metrics` or `signal_type: logs` key.
/// Full configuration for running multiple concurrent scenarios.
///
/// Deserialized from a multi-scenario YAML file that contains a top-level
/// `scenarios:` list. Each entry specifies its `signal_type` (either `metrics`
/// or `logs`) along with the scenario-specific fields.
///
/// # Example YAML
///
/// ```yaml
/// scenarios:
/// - signal_type: metrics
/// name: cpu_usage
/// rate: 100
/// duration: 30s
/// generator: { type: sine, amplitude: 50, period_secs: 60, offset: 50 }
/// encoder:
/// type: prometheus_text
/// sink:
/// type: stdout
/// - signal_type: logs
/// name: app_logs
/// rate: 10
/// duration: 30s
/// generator:
/// type: template
/// templates: [{ message: "event", field_pools: {} }]
/// encoder:
/// type: json_lines
/// sink:
/// type: file
/// path: /tmp/logs.json
/// ```
/// Full configuration for a single log scenario run.
///
/// Deserialized from a YAML scenario file. CLI flags can override any field.
///
/// # Example YAML
///
/// ```yaml
/// name: app_logs
/// rate: 10
/// duration: 60s
/// generator:
/// type: template
/// templates:
/// - message: "Request from {ip} to {endpoint}"
/// field_pools:
/// ip: ["10.0.0.1", "10.0.0.2"]
/// endpoint: ["/api", "/health"]
/// severity_weights:
/// info: 0.7
/// warn: 0.2
/// error: 0.1
/// encoder:
/// type: json_lines
/// sink:
/// type: stdout
/// ```