Runs and transferred files

Every file a transfer moves leaves a record. rclone writes one log line per file while the run is still going, and the run ends with one summary of the files, the bytes and the errors. You read them in the admin UI, with the CLI, or in your own systems through telemetry forwarding.

A run and its files#

The transfer’s page in the admin UI has a Runs section with one row per run. A run opens inside the section with its start and end, the operation, the source and destination, the counts and the files it moved, each with its size.

/integrations/finance/supplier-invoices/runs

Integrations › Transferred files lists the files of every transfer in one table, so you can check that one file arrived without knowing which transfer moved it.

/integrations/files

The log line of each file#

$ weikio logs finance/supplier-invoices --env production --since 24h

The command prints each line as rclone wrote it, one JSON object after the time, the level, the route mft-log and the agent. Every line is written at INFO, with rclone’s own level in its level field. A moved file is a line whose msg says Copied or Moved, with the file in object and its size in size, and a run ends with a line of rclone’s stats: the files transferred, the bytes and the errors.

These lines are the transfer’s file-level audit trail, kept for as long as the installation keeps its logs, 30 days by default. Each one carries the integration, the version, the project, the environment and the agent, and the same permissions apply to them as to every other log line.

The run summary#

Each run publishes one summary into the environment’s event stream. Other integrations react to it, and you can list it:

$ weikio events list --env production --family mft --integration finance/supplier-invoices --since 24h --with-body

The list has one row per run, and --with-body adds the summary itself: the run’s ID, its start and end, the files, the bytes, the errors and the first error rclone wrote. Every log line of the run carries the same ID as its correlation ID, so one run’s lines are read by it:

$ weikio logs finance/supplier-invoices --env production --since 24h --correlation-id 5f0c6d2e-8a41-4b7e-9c3d-2a1e7b9f4c60

When the site’s link to the hub is down for a moment, the agent publishes the summary again, waiting longer each time, for about five minutes.

A failed run#

A run that ends with errors fails, in the words of its first error. It counts as a failed message in weikio status, weikio metrics and the admin UI, and it raises a problem that points to the run and gives the weikio logs command that shows what rclone wrote in it. The problem shows in Home’s Needs attention, on the Observability Overview, on the transfer’s page and in weikio problems, and it clears when a later run counts no errors.

/integrations/finance/supplier-invoices/runs

A missing folder, a refused password and a full disk at the destination all end the same way: the first error is in the run’s summary, and the lines around it are in the logs under the run’s correlation ID.

When the installation keeps no logs#

An installation set up with --no-observability has no log store, so it keeps no record of the files. The files of a run and Transferred files then say Transfer history isn't stored here, and the Runs section still lists the run summaries from the event stream. Telemetry forwarding sends the same lines to your own log system.