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
//! Optional telemetry seam for AEROVAULT3 operations.
//!
//! The crate's vault operations are pure and emit no telemetry by default. An
//! embedder (the AeroFTP application, mainly) can attach a [`VaultTelemetrySink`]
//! to an [`OpenVaultV3`](super::vault::OpenVaultV3) via
//! [`set_telemetry_sink`](super::vault::OpenVaultV3::set_telemetry_sink) to
//! receive a behind-the-scenes "receipt" of what the content pipeline did
//! (chunking, dedup, compression, packing, Error Correction) without the crate
//! depending on the embedder's report type.
//!
//! The events mirror the instrumentation points the application historically
//! inlined, so the receipt it builds is byte-for-byte the same as before the app
//! converged onto the crate. When no sink is attached every call is a no-op and
//! the produced container bytes are unchanged (the T5 golden proves this).
// SPDX-License-Identifier: GPL-3.0-only
/// A sink that receives technical telemetry events as an AEROVAULT3 operation
/// runs. All methods default to no-ops so an embedder only implements what it
/// needs. Must be `Send` so an [`OpenVaultV3`](super::vault::OpenVaultV3) carrying
/// one can move into a blocking worker thread.