• Queued File Transfer Jobs - This gauge-type metric represents the queued file transfers in the ThingWorx instance at that time. The file transfer job is created and queued in the offline queue as soon as the file transfer is triggered. The metric name is queuedTransferJobs under the GetPerformanceMetrics service of the File Transfer subsystem. For external consumption like Prometheus, this would be available as thingworx_FileTransferSubsystem_queuedTransferJobs under the /Thingworx/Metrics endpoint.

• Active File Transfer Jobs- This gauge-type metric represents the active file transfers in the ThingWorx instance at that time. When file transfer is activated, the transfer job is moved from an offline queue to an active queue. This metric represents the active file transfers. The metric name is activeTransferJobs under the GetPerformanceMetrics service of the File Transfer subsystem. For external consumption like Prometheus, this would be available as thingworx_FileTransferSubsystem_activeTransferJobs under the /Thingworx/Metrics endpoint.

• File Transfer Metrics - There are additional metrics available for file transfers. All these metrics are counter type. The metrics are based on the type and state of the File Transfer. File Transfer types are upload, download, and between repositories. File Transfer States are Started, Completed, Cancelled, and Failed. Different metrics are available for the combination of different types of file transfers. For external consumption like Prometheus, this would be available as thingworx_FileTransferSubsystem_{upload/download/acrossRepo}{Started/Completed/Cancelled/failed}Transfers_total, under the /Thingworx/Metrics endpoint.