@bli-cockpit/telemetry-core 0.1.31 → 0.1.32
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -58,6 +58,8 @@ export declare const CollectorHeartbeatSchema: z.ZodObject<{
|
|
|
58
58
|
sessions_outside_root: z.ZodOptional<z.ZodNumber>;
|
|
59
59
|
sessions_new_this_tick: z.ZodOptional<z.ZodNumber>;
|
|
60
60
|
sessions_pending_upload: z.ZodOptional<z.ZodNumber>;
|
|
61
|
+
staging_uncommitted_bytes: z.ZodOptional<z.ZodNumber>;
|
|
62
|
+
staging_uncommitted_reason: z.ZodOptional<z.ZodString>;
|
|
61
63
|
memory_install: z.ZodOptional<z.ZodObject<{
|
|
62
64
|
schema_version: z.ZodLiteral<"memory-install-receipt.v1">;
|
|
63
65
|
checked_at: z.ZodString;
|
|
@@ -114,6 +114,37 @@ export const CollectorHeartbeatSchema = z
|
|
|
114
114
|
.nonnegative()
|
|
115
115
|
.max(1_000_000)
|
|
116
116
|
.optional(),
|
|
117
|
+
/**
|
|
118
|
+
* BLI-3797. How many staged raw-evidence bytes on this machine the upload
|
|
119
|
+
* ledger cannot vouch for, and the one label that explains most of them.
|
|
120
|
+
*
|
|
121
|
+
* These are the "collection has not landed" numbers. A machine can be
|
|
122
|
+
* alive, syncing, green on every other counter here and still be holding
|
|
123
|
+
* gigabytes of transcript that never reached storage — on the reference Mac
|
|
124
|
+
* 1,836 MB across 234 objects, the oldest staged 45 days earlier, with the
|
|
125
|
+
* server itself answering `unknown_to_server` when asked. Nothing in this
|
|
126
|
+
* heartbeat could say so, so `cockpit ops` could not either.
|
|
127
|
+
*
|
|
128
|
+
* `staging_uncommitted_reason` follows `last_sync_reason`'s
|
|
129
|
+
* `nothing_in_root:47` idiom — `<dominant reason>:<object count>` — so one
|
|
130
|
+
* bounded label carries both halves and a reader prints it verbatim rather
|
|
131
|
+
* than parsing it. Both fields are optional: a collector too old to compute
|
|
132
|
+
* them keeps posting, and an absent value reads as "this collector predates
|
|
133
|
+
* the counter", never as "this machine holds nothing".
|
|
134
|
+
*/
|
|
135
|
+
staging_uncommitted_bytes: z
|
|
136
|
+
.number()
|
|
137
|
+
.int()
|
|
138
|
+
.nonnegative()
|
|
139
|
+
.max(Number.MAX_SAFE_INTEGER)
|
|
140
|
+
.optional(),
|
|
141
|
+
staging_uncommitted_reason: z
|
|
142
|
+
.string()
|
|
143
|
+
.trim()
|
|
144
|
+
.min(1)
|
|
145
|
+
.max(120)
|
|
146
|
+
.regex(/^[a-z0-9_:.-]+$/iu)
|
|
147
|
+
.optional(),
|
|
117
148
|
/**
|
|
118
149
|
* BLI-3729. Is BLI Memory actually switched on for both agent hosts on
|
|
119
150
|
* this machine? Six words computed by reading the host configs BACK, not
|