Use cases
Jobs where this local tool earns its keep. Each names the role, the task before the deadline, the steps, and what done looks like.
1. Observability engineer migrating internal Explore scripts
Who: An observability engineer owning Python/TS scripts that call /events/ with dataset=transactions.
Task: Finish migration before Dec 3 so nightly reports do not 400.
Steps: Inventory endpoints; answer home axes; apply field/function map; add is_transaction:true; smoke; attach Markdown.
Result: No script relies on retired datasets after the cutoff.
2. SRE splitting mixed discover dashboards-as-code
Who: An SRE whose dashboards-as-code still use discover for both errors and transactions.
Task: Split into errors+spans requests and reconcile panels.
Steps: Mark mix=both; dual requests; update field names; export map into the change request.
Result: Dashboards render without dataset errors after Dec 3.
3. On-call triage when a third-party integration starts failing
Who: An on-call engineer after the cutoff email window.
Task: Decide whether failure is missing dataset, field rename, or mixed discover.
Steps: Walk the home map with discover/default; check is_transaction and function list; open a vendor ticket with the export.
Result: Incident notes separate dataset work from unrelated SDK issues.
See also How-to and FAQ.