Monitor¶
The monitoring service monitors packets and keeps track of other stations the station has heard. It is enabled by default.
Station tracking¶
The monitor keeps track of stations it has heard. You can get a list of all stations the monitor has heard by accessing station.monitor.heard_stations. You can also use the included cli app's heard command to view the stations on the command line.
To preserve station tracking data between restarts, set the memory_file path in the Monitor Settings. The monitoring settings are set as the monitor key in the Station Config dictionary.
Logging¶
The monitoring service logs packets on gateway interfaces not related to a connection in the connection table.
Note
In the future, packets may be logged even for active connections.
Custom Listeners¶
Listeners can be registered for monitored packets. Registering a listener is done with the .register_listener function, documented below. Each listener must have a unique label. Duplicate labels will be logged with a warning, and will override the previous usage.
Listener functions must return a boolean value. If the value is True, the log entry will be considered 'consumed' and won't be retained by the service for later consumption.
Consuming Log Entries¶
The log entries that have been stored in the monitoring service may be explicitly consumed with the consume_logs method, which will return an iterable with all log entries and empty the current log.
Heard Command¶
The 'heard' command is provided by the monitoring service. This command returns all stations that have been heard on the gateway interfaces. It comes in three notation forms-- the standard form, the short form, and the long form. The command is made available as a property on the monitoring service (.command) for easy inclusion into client applications, such as the contributed CommandLine app.
The long form of the command is unique among packet stations with similar commands. The long form not only includes the 'vias' (digipeaters) but also the last heard Unnumbered Information frame. This makes it easier to determine what kind of services the remote station may have, as stations frequently send out beacons with information about what services they provide.
pax25.types.MonitorSettings
¶
Settings for monitoring.
Source code in pax25/types.py
pax25.services.monitor
¶
Monitoring service module.
The monitoring service allows the station to keep track of traffic it has heard, and keep reference tables that can be used. Comes with a couple of commands that you can add to other applications.
HeardEntry
dataclass
¶
Log entry for heard stations.
Source code in pax25/services/monitor.py
LoggedFrame
dataclass
¶
Monitor
¶
Service that monitors incoming packets and keeps track of information like what stations have been heard and what they've said about themselves.
Source code in pax25/services/monitor.py
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 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 | |
command: CommandSpec[HeardOptions]
property
¶
Builds a command spec for the heard command.
heard_stations: dict[str, HeardEntry]
property
¶
Return a tuple of heard stations.
settings: MonitorSettings
property
¶
Return the monitor's current settings.
__init__(*, station: Station, settings: MonitorSettings | None)
¶
Initializes the monitoring service.
Source code in pax25/services/monitor.py
add_listener(label: str, listener: LogListener) -> None
¶
Registers a frame listener.
Source code in pax25/services/monitor.py
consume_logs() -> list[LoggedFrame]
¶
heard(connection: Connection, context: CommandContext[HeardOptions]) -> None
¶
Heard command. Can be included using the 'command' property on the monitoring service, which defines a CommandSpec for inclusion in other apps.
Source code in pax25/services/monitor.py
load_stations() -> None
¶
Load heard stations from a save file.
Source code in pax25/services/monitor.py
log_frame(frame: Frame, interface: Interface) -> None
¶
Log a frame heard on a gateway.
Source code in pax25/services/monitor.py
refresh_ports_cache() -> None
¶
reload_settings(settings: MonitorSettings) -> None
async
¶
Reload monitoring settings.
Source code in pax25/services/monitor.py
remove_listener(label: str) -> None
¶
Removes a frame listener.
Source code in pax25/services/monitor.py
run() -> None
¶
save_loop() -> None
async
¶
Loop that periodically saves all the stations we've heard.
Source code in pax25/services/monitor.py
save_stations() -> None
async
¶
Save all the known stations to a file for later retrieval.
Source code in pax25/services/monitor.py
shutdown() -> None
async
¶
Shut down the monitoring service.
Source code in pax25/services/monitor.py
update_entry(frame: Frame, interface: Interface) -> None
¶
Updates the entry in the heard table.