Viewing Sync transfers in the Aspera GUI

The HSTS GUI shows async-initiated transfers if Sync is run on the machine (as client) by default, whereas server async transfers are not shown.

In the following example, the GUI shows transfers that are associated with a Syncjob in which the remote user, Aspera, is pushing files to the server folder for Project X.

Example: Transfers associated with Syncjob and the Aspera user

You can configure the server and client reporting to the Aspera GUI with the following options.

Server reporting:

Server reporting is disabled by default. To enable the server to report Aspera Sync-initiated transfers:

  1. Run the following command on the server:
    # asconfigurator -x "set_node_data;async_activity_logging,true"
  2. Restart asperanoded to activate your changes.
    Run the following commands to restart asperanoded:
    # systemctl restart asperanoded
    or for Linux systems that use init.d:
    # service asperanoded restart

Client reporting:

Client reporting is enabled by default. To disable the client from reporting Aspera Sync-initiated transfers, run the following command on the client machine:

# asconfigurator -x "set_client_data;async_management_activity_logging,false"

You do not need to restart asperanoded for this change to take effect.