Cloud Incident and Replay

ByteOr Cloud provides an integrated incident capture and replay workflow through the control plane.

Artifact Collection

Agents upload artifacts to the control plane:

  • Incident bundles from incident-bundle captures
  • State snapshots from snapshot captures
  • Runtime diagnostic outputs

Artifacts are stored with metadata including agent, environment, capture time, and content hash.

Investigation Flow

  1. Identify the incident, agent, deployment, and environment
  2. Open the stored artifact record in the Cloud UI
  3. Confirm artifact metadata and capture time
  4. Launch a dry-run replay to validate the reconstructed input
  5. Review the replay audit result
  6. Escalate to execute-mode replay only when the environment posture and approval coverage allow it

Dry-Run Replay

Use dry run for investigation:

  • Inspect behavior without executing against live infrastructure
  • Validate that the captured input reproduces the issue
  • Confirm the pipeline version matches the incident
  • Test remediation strategies

Execute-Mode Replay

Use execute mode only when:

  • Dry run confirms the issue
  • The environment posture permits governed execution
  • A matching pipeline version can be resolved
  • Approval coverage is attached

The backend validates all prerequisites before allowing execution to begin.

Monitoring Replay

Cloud surfaces replay status:

  • Replay request creation and authorization check
  • Pipeline version resolution
  • Execution status and progress
  • Resulting audit records

Operational Escalation

Escalate when:

  • The source environment cannot be resolved
  • The artifact spec hash does not map to a known pipeline version
  • Approval coverage is missing or rejected
  • The agent shows repeated authorization failures during investigation
Provenance
Need the canonical source?
Use the public hub to orient yourself, then jump to repo-owned docs or rustdoc when you need contract-level detail.