Snapshots off and monitoring off

​

Snapshots off

• Nothing of the sandbox is stored outside its machine.
• No background work runs on it.
• A stop erases it.
• You cannot resume it, fork it or save it as a named snapshot.
• If its machine fails, there is no backup.

​

Turn snapshots off for the whole account

1. Open the Account tab.
2. Under Data & privacy, turn on Snapshots off.

​

Turn snapshots off for one sandbox

boat new --no-snapshots

curl -sS -X POST "$BOAT_API_BASE/sandboxes" \
  -H "Authorization: Bearer $BOAT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"snapshots":false}'

await sandbox.create({ snapshots: false });

from boat_sdk.models.create_sandbox_request import CreateSandboxRequest

sandbox.create(CreateSandboxRequest(snapshots=False))

​

Monitoring off

• The sandbox runs no process tracer.
• Disk-full alerts need CPU/RAM samples. They are not available for this sandbox.
• The cause shown for a lost sandbox needs CPU/RAM samples. It is not available for this sandbox.
• Its history, processes and metrics calls return 409 monitoring_off.

​

Turn monitoring off for the whole account

• On the Account tab, under Data & privacy, turn on Monitoring off.
• Send PATCH /account/data-retention with {"monitoringOff": true}.

​

Turn monitoring off for one sandbox

boat new --no-monitoring

curl -sS -X POST "$BOAT_API_BASE/sandboxes" \
  -H "Authorization: Bearer $BOAT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"monitoring":false}'

await sandbox.create({ monitoring: false });

from boat_sdk.models.create_sandbox_request import CreateSandboxRequest

sandbox.create(CreateSandboxRequest(monitoring=False))