Telemetry stopped after a tenant reset

What you're seeing

After your organization's tenant was reset (the nuclear option: organization data dropped and rebuilt from scratch): the app looks healthy, the emitter still shows active in Setup — but no new records arrive, and within hours an Emitter silent finding fires. On the emitter host, the SDK logs show batches being refused with 401 "unknown collector".

What it means

A reset drops the organization's database — including the emitter's registered public key. The platform-level registry still lists the emitter as active (that is a different table), so nothing on screen says ingest is failing until the silence finding fires. Batches signed with the old key no longer verify against anything, and ingest rejects them.

The emitter's spool still holds every batch since the reset, signed with the key it has on disk — and that is what saves you.

What to do

  1. Re-register the emitter with its existing public key — do not generate a new one. On the Setup page's Register an emitter card, use the bring-your-own-key path and paste the same public key the emitter already has (PROVANTIX_PRIVATE_KEY_PEM on the emitter host derives it). A fresh generated key would reject every spooled batch as a bad signature.
  2. Once the collector row exists with the old key, restart the emitter (or wait for its next flush). The SDK retries spooled batches in order; they verify and land.
  3. Expect one sequence_gap finding on the first accepted batch: the new collector row restarts at sequence zero while the emitter continues from its old counter. That is correct behaviour, not data loss — the hole marks exactly where the reset happened. Resolve it with the reason "tenant reset on ; emitter re-registered with existing key".
  4. Verify: records newer than the reset appear in Investigate, the agent re-attributes within about 15 minutes, and the silence finding resolves.

What good looks like

All spooled batches landed with their original signatures, the chain shows one explained gap at the reset point, and the decision log records the re-registration with your name on it.

Prevention

Tenant resets are a runbook procedure, not a habit. Before the next one: export anything you might need (findings history, attestations, the audit log) — none of it survives — and note that re-registering emitter keys is a mandatory post-reset step, exactly like this page says.