DATABRICKS
Databricks
Databricks Jobs

Job-level Auto Tune enabled/disabled events for chart markers

Changed on

Enable/disable events across every task under this job, for the Cost Savings chart's vertical markers.

Each user toggle click writes one job-level JOB_AUTO_TUNE_ENABLED / JOB_AUTO_TUNE_DISABLED row, which is the marker for that click (one per click and direction, however many tasks it touched). History written before those rows existed has no such row: its human APPLY_REQUESTED (enable) and REVERTED (disable) rows, one PER TASK, are returned as markers instead. Slot rows stamped with toggle_audit_id are skipped so a click is never marked twice; system re-arms, recovery requeues, and unattributed legacy requests are not toggle markers. entity_type is intentionally NOT filtered on, mirroring /auto-tune/history above — the toggle pipeline and the entity-generic config pipeline stamp different entity_type values for job rows, so filtering on it risks silently dropping real events.

get/api/v1/databricks/jobs/{job_id}/auto-tune/toggle-events

Request

  • Base URL: https://api.myaltimate.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.myaltimate.com/api/v1/databricks/jobs/{job_id}/auto-tune/toggle-events
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

job_idstring required

Query parameters

instance_idinteger required

Tenant instance ID (workspace) the job runs in

workspace_idstring nullable

Optional Databricks workspace_id to scope the lookup. Defends against cross-workspace job_id collisions.

start_datestring date nullable

Start date

end_datestring date nullable

End date

Headers

x-tenantstring required

Response

Successful Response

Changes