Paginated Auto Tune audit history for a job
Changed onRead-only audit history for the Auto Tune tab.
Returns the most-recent events first. Each row carries event_message composed server-side from event_type + mode + actor
- payload via DBX_AUTO_TUNE_EVENT_UI_MAPPING so the FE renders one string verbatim.
User resolution is manual (PR #5070 hasn't merged): we batch-load altimate_users rows for displayed rows and any request rows used for APPLIED provenance. A separate lightweight MUTATION_STARTED query follows exact request links without exposing those markers in history.
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/history
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
Query parameters
Tenant instance ID (workspace) the job runs in
Comma-separated list of event_type values to include. Empty/omitted defaults to the 5 customer-relevant states (APPLY_REQUESTED, APPLIED, REVERTED, BACKOFF, FAILED). Pass explicit values (e.g. MUTATION_STARTED, CANCELLED) to escape the default for internal/debug use.
Look-back window in days. Excludes audit rows whose change_timestamp is older than now - period days.
Optional Databricks workspace_id to scope queries to a specific workspace within the tenant's Databricks account. Defends against cross-workspace job_id collisions. When None, falls back to (instance_id, entity_id) lookup.
Page number (1-indexed)
Items per page
Headers
Response
Successful Response
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info