upload block is
deployed to a device, the Miru Agent handles the rest: detecting when a matching file is
finished, uploading it to your bucket, and recording it in the ledger with the
properties below.
Properties
Destination
Where the collected file was uploaded. See Destinations.
string
The digest of the uploaded file. Used to deduplicate uploads, so each file is
uploaded exactly once, and to verify integrity.Example:
sha256:1234567890integer
The size of the uploaded file, in bytes.
datetime
Timestamp of when the upload was durably confirmed. Null until the upload completes.
Deployment
The deployment that was active on the device when the
upload was produced.
created_at, updated_at, and workspace_id
bookkeeping fields.
Sources
An upload’ssource identifies the file collected from the device and when it was
last modified.
string
Absolute path of the file on the device. Its basename renders the
{file_name}
variable in the upload path template.Example: /var/log/robot/robot.logdatetime
The file’s
mtime timestamp as reported by the operating system.datetime
The timestamp of when the file was first observed by the Miru Agent for this upload.
datetime
The timestamp of when the file was last observed by the Miru Agent for this upload.
Destinations
An upload’sdestination identifies the bucket and object key where the file was
written.
string
The object path the file was written to in the destination bucket. Rendered from the
rule’s path template, it carries the device’s verified ID.Example:
logs/dvc_123/upl_123/robot.logStatus
An upload’s status tracks whether the device has confirmed that the file was durably written to the destination bucket.
Uploads begin in the
pending state. A device may retry or resume the transfer while
the upload remains pending. After the device confirms the durable write, the upload
transitions to uploaded, which is its terminal state.