Example use cases for monitoring transfer activity

How do I find the public link associated with a transfer?

You must be an organization admin to complete this procedure.

The Details panel for each public link transfer event includes the URL token for both standard-form and short/personalized-form links. Having both tokens means that you can find and manage the link even if the Admin has reset the URL style since the link was issued. Both tokens refer to the same link, and you can find one token or the other as you manage public links in the Files or Packages apps.

1. Go to Activity > Transfer activity.
2. In the Transfers table, click the row of the transfer that lists "Public link" in the Started by column to open the Event details panel.
3. Check the Event field:
   1. A file or folder event (for example, "File upload" means the link was sent from the Files app.
   2. A package event (for example, "Package sent") means the link was sent from the Packages app.
4. Note the links and tokens:
   1. In the Started by or From field, note the public link. This is the link that the user sent.
   2. In the Tokens fields, note the Standard and Short/personalized tokens. These tokens are different forms of the same public link in the Started by or From field.
   3. If you configured the Files and Packages apps to use personalized URL formats with the link sender's name (best practice), you can readily see who sent the public link. You cannot tell who used the public link to transfer.
5. Note the workspace.
6. To search for the link in the Files app, do the following:
   1. In the Files app, go to the workspace listed in the Activity transfer Event details panel. Click a shared folder to open the folder Details panel.
   2. Below the list of collaborators, click Manage all links.
   3. In the public links listing, look for one of the tokens you noted in the Activity app Details panel.
7. To find the link from the Packages app, do the following:
   1. In the Details panel, note the recipient in the To field. If this is a shared inbox, go to the Packages app and enter the shared inbox.
   2. In the right panel below the list of members, click Manage all links.
   3. In the Public link section, locate any of the link tokens you noted in the Activity app.

Is someone using an excessive amount of bandwidth?

1. Go to Activity > Transfer activity.
2. Click the filter marked All, and select User.
3. In the search box, enter a user name and click the name when it appears in the list.
4. Click the time filter and select a time range.
5. In the graph, examine upload and downloads for that user. In the tables below, you can see a breakdown of the bandwidth for the resources (workspaces and nodes) used by that user.

How can I diagnose the problem with a failed transfer?

1. Go to Activity > Transfer activity.
2. Find the failed transfer: filter by date, workspace, user, or other data, depending on the initial information you have.
3. In the table, check the Event column to determine the transfer type.

   The table represents an upload or download on a single line. A node-to-node transfer occupies two lines in the table; Activity app reports both directions of a node-to-node transfer.

4. In the Status column, hover over the Status field to display the error message.

Example: Upload

• The transfer type listed in the Event column is confirmed by the Node, Direction, and Peer columns as follows: The node "tor04_node" received the transfer from a peer with the IP address listed. Presumably the peer is the local computer of the user listed in the Started by column.
• In the Status column, click the error.
• Search the user documentation for the error label "Session data transfer timeout".

Example: Node-to-Node Transfer

• The two rows show the two directions of the same node-to-node transfer.
• Check the Node and Peer columns. Since node and peer are the same ("aejd2"), the transfer was from one location on the node aejd2 to a different location on the same node aejd2.
• In the error message displayed in the screenshot, the text states that it was the client that reset the connection. Since this message displays at the IP address 127.0.1.1, we can see that the client is at IP 127.0.0.1. So the client is initiating a transfer from the server at 127.0.1.1.
• Search the web for the error "Connection reset by peer". In most cases, this error means that the remote end of the transfer dropped the TCP connection without the expected state transition. A first course of action would be to retry the transfer.

Which packages on a particular node have failed in the last day?

1. Next to Bandwidth usage by, select Node from the menu.
2. From the Choose Node menu, select the desired node, then from the in menu, select "Last 1 day".
3. Scroll down to the bottom panel and click Failed.
4. You can now examine the list of failed transfers of type, "Package". Click a transfer row to view event details.