Remediation create
Creates a new remediation for an instance.
Remediations created via the API goes directly to PENDING state.
Our system may trigger automated remediations that require approval. These remediations are created with PENDING_APPROVAL state. The user must call /approve to start the actual remediation process. These operations can also be rejected by calling /reject.
Documentation Index
Fetch the complete documentation index at: https://docs.together.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Client-specified ID for idempotency.
Body
Remediation represents a node remediation request for an instance. An instance can have multiple remediations over time (e.g., failed attempts followed by retries).
Remediation mode specifies how the remediation should be performed.
REMEDIATION_MODE_VM_ONLY: Deletes the VM and provisions a new one on any available host.REMEDIATION_MODE_HOST_AWARE: Cordons the host, deletes the VM, and provisions a new one on a different host.
REMEDIATION_MODE_VM_ONLY, REMEDIATION_MODE_HOST_AWARE, REMEDIATION_MODE_EVICT_WITHOUT_REPLACEMENT, REMEDIATION_MODE_REBOOT_VM User-provided reason for the remediation.
Response
OK
Remediation represents a node remediation request for an instance. An instance can have multiple remediations over time (e.g., failed attempts followed by retries).
Remediation mode specifies how the remediation should be performed.
REMEDIATION_MODE_VM_ONLY: Deletes the VM and provisions a new one on any available host.REMEDIATION_MODE_HOST_AWARE: Cordons the host, deletes the VM, and provisions a new one on a different host.
REMEDIATION_MODE_VM_ONLY, REMEDIATION_MODE_HOST_AWARE, REMEDIATION_MODE_EVICT_WITHOUT_REPLACEMENT, REMEDIATION_MODE_REBOOT_VM RemediationTrigger specifies how the remediation was triggered.
REMEDIATION_TRIGGER_MANUAL: A user-initiated remediation (either via web UI or API call).REMEDIATION_TRIGGER_AUTOMATED: A system-initiated remediation that requires approval.
REMEDIATION_TRIGGER_MANUAL, REMEDIATION_TRIGGER_AUTOMATED RemediationState represents the lifecycle state of a remediation.
PENDING_APPROVAL: Awaiting approval before processing can begin.PENDING: Approved and queued for processing.RUNNING: Actively being processed.SUCCEEDED: Successfully completed.FAILED: Failed with an error.CANCELLED: Cancelled by user or system.AUTO_RESOLVED: The underlying issue was automatically resolved before processing.
PENDING_APPROVAL, PENDING, RUNNING, SUCCEEDED, FAILED, CANCELLED, AUTO_RESOLVED User-provided reason for the remediation.
Active health check run ID (UUID) that triggered this remediation.
Passive health check event ID that triggered this remediation.
Who requested the remediation.
When the remediation was created.
Who reviewed the remediation.
When the remediation was reviewed.
Review comment.
When processing started.
When the remediation completed.
Error message if the remediation failed.
When the remediation was last updated.
Display name of the targeted instance.