EXTENSIONS
Built by operatives — models, drivers, vaults, and reports, the parts that plug into Swamp.
Filter by what you need and pull what fits.
Triage Snapshot
Workflow-scope report that renders a one-look snapshot of the
Gcp/health
Google Cloud health infrastructure models
Coder Health Probe
Polls Coder server health and build info endpoints. Produces typed health state with latency measurements for reliability analysis.
K8s Fleet
Fleet-wide Kubernetes health across all kubeconfig contexts. Iterates every cluster in ~/.kube/config (or a specified subset) and produces per-cluster health snapshots plus an aggregated fleet summary. Best-effort — unreachable clusters are reported, not fatal.
Peloton Rides
Read your Peloton workout history, per-ride metrics, and the on-demand class library via Peloton's unofficial api.onepeloton.com API. Auth0 Bearer-token auth from a vault-stored refresh token (self-renewing, access-token cached; short-lived accessToken fallback). Decomposed data model: each workout is its own addressable `ride` resource and each library class its own `class` resource, keyed by id — query with `swamp data query`/CEL, no list blob. Methods: getRecentRides (factory; one ride resource per workout), getRideDetail (enriches a ride in place with total/avg/max output, cadence, resistance, speed, heart rate, distance, calories, downsampled series), getStats (derived aggregate rollup), browseClasses (factory; browse the class library filtered by discipline/instructor/type/duration/difficulty, one class resource per match). No official Peloton API exists; this mirrors the web app's endpoints and may break if Peloton changes them.