Incidents — fired when a secret is found (PII isn't alerted on by default). Deduped per leaked secret (occurrence count rises instead of flooding). Prod = critical.
| Sev | Title | Where | Seen | Last | |
|---|---|---|---|---|---|
| no alerts — nice 🎉 | |||||
Delivery & heartbeat (optional)
Push incidents to Slack and get warned when a service goes quiet. Both optional — leave blank to disable.
Heartbeat needs a periodic poke. Add a cron job:
*/10 * * * * curl -fsS -X POST -H "Authorization: Bearer trk_admin_local" http://localhost:8000/v1/heartbeat/check
Where each redacted event came from — code origin (file:line · function), service/env — so you can trace a finding back to the source. Never any raw values.
| Time | Source | Origin | Findings | Categories |
|---|---|---|---|---|
| no events yet | ||||
| Detector | Count |
|---|---|
| no findings yet | |
Ingest keys for this project. Rotate by minting a new key, deploying it to your SDK, confirming it shows a recent "last used", then revoking the old one. The full key is shown once, at creation — store it now.
| Label | Key | Status | Last used | From IP | |
|---|---|---|---|---|---|
| no keys | |||||
Immutable activity log for this project — who changed what, when (projects, policy, keys). Read-only.
| Time | Actor | Action | Target | Details |
|---|---|---|---|---|
| no activity yet | ||||
Policy for the selected project (JSON). Save → the SDK pulls it on its next poll. Test changes locally with the FOSS CLI; don't paste real data here.