Properties
Where the collected file was uploaded. See Destinations.
The digest of the uploaded file. Used to deduplicate uploads, so each file is
uploaded exactly once, and to verify integrity.Example:
sha256:1234567890The size of the uploaded file, in bytes.
Timestamp of when the upload was durably confirmed. Null until the upload completes.
The upload rule that produced the upload.
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.
Absolute path of the file on the device. Its basename renders the
{file_name}
variable in the destination path template.Example: /var/log/robot/robot.logThe file’s
mtime timestamp as reported by the operating system.The timestamp of when the file was first observed by the Miru Agent for this upload.
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.
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.