Rucio Traces

Note: this page is VO specific / users of Rucio

The Pilot sends detailed information about file transfers to Rucio. Here is a list of the different fields contained in the trace report.

Field name	Type	Meaning
appid		PanDA job id
catStart		Time stamp when Rucio has been queried for replica information
clientState		State at the time the trace is sent; e.g. INIT_REPORT, STAGEIN_FAILED, NO_REPLICA, STAGEIN_NOTALLOWED, STAGEIN_ATTEMPT_FAILED, STAGEOUT_ATTEMPT_FAILED, DONE
dataset		Dataset name (prodDBlock from job definition - or destinationDblock)
guid		(currently not set by the Pilot)
eventType		Type of trace; currently the following event types are sent by the pilot (ordered by frequency; in the case of user jobs, an _a is added to the type): 1. get_sm_a: stage-in inputs for user analysis jobs 2. get_sm: stage-in inputs for non-analysis jobs 3. put_sm: stage-out outputs for non-analysis jobs 4. get_es: stage-in inputs for eventservice jobs 5. download: EXPLANATION MISSING 6. put_sm_logs: stage-out logs for non-analysis jobs 7. put_sm_a: stage-out outputs for analysis jobs 8. put_sm_logs_a: stage-out logs for analysis jobs 9. upload: EXPLANATION MISSING 10. put_es: stage-out outputs for eventservice jobs 11. put_sm_logs_os: stage-out logs to objectstore (special transfer defined in CRIC per panda queue)
eventVersion	String	Pilot version
filename	String	the local file name (LFN)