telemetry-probe

telemetry-probe

Every "probe it, then clean up" in this repo used to be a hand-written script, and it went wrong in the same places each time (2026-10-16/17):

• deleting with GlitchTip's read-only token (403);
• the legacy /store/ endpoint, which drops debug_meta;
• forgetting the Umami session row;
• calling a delete done before the re-read showed it gone.

This skill does it the tested way.

Run (on the mini, through host-run)

P=~/.claude/skills/telemetry-probe/scripts/probe.py
R=~/.claude/skills/host-run/scripts/run.sh

$R homelab $P glitchtip --project player-dev --assert-absent player,player-api
$R homelab $P umami     --site "Player (dev)" --assert-absent Player
$R homelab $P langfuse  --keys '~/podcast-langfuse-dev.env'

Option	Meaning
--project / --site	the GlitchTip project slug, or the Umami site name or id, that should receive the probe
--assert-absent a,b	targets that must not receive it; this is the isolation check (dev vs prod)
--keys FILE	Langfuse: the env file with that project's key pair (see the handbook, section 8)
--keep	leave the probe in place, e.g. as a baseline another agent asked for

Labels: every probe is labelled zz-probe-<utc>, with GlitchTip environment=probe and Umami hostname telemetry-probe.localhost. Nothing real is mistaken for one.

Exit 0 / PROBE: PASS only when all three hold:

1. the probe landed in the target;
2. it is absent from every --assert-absent target;
3. unless --keep, the delete was accepted and a re-read shows it gone.

How each service is done

• GlitchTip:
  • sends a Sentry envelope to /api/<id>/envelope/ (not /store/), using the project's own DSN key;
  • reads with the fleet's read-only token;
  • deletes through the superuser session login (the handbook's curl recipe), then waits for a 404.
• Umami:
  • POSTs /api/send with a browser User-Agent. Umami's bot filter answers 200 {"beep":"boop"} and stores nothing for non-browser UAs; the script detects that.
  • checks website_event, then deletes the event, its event_data, and the session if nothing else uses it, in one transaction.
• Langfuse:
  • trace-create through /api/public/ingestion, read back by id;
  • DELETE is asynchronous, so the script waits for a 404.