Two axis to work on (potentially in parallel):

• Runtime traceability: finding more details (e.g user identifier) about a running job from artefact left by the pilot/VO framework (file name, log files, etc)
  • Needed for a better challenge capable of validating the VO findings
  • Actions on VOs: identify what is already available and can be collected
• Offer a possibility for sites to collect these logs (like FNAL for CMS):
  • HTCondorCE has a new feature, which can produce audit logs if the jobs push backs the right information.
    • Dave will share a command line that can be used to produce that data
    • This does not cover all CEs and might only be a gap solution
  • What should be required from VO?
    • First estimation: Start/stop action, user unique identifier (opaque string)
    • More debug information from VOs? (e.g. pilot id, job id for the pilot framework, etc)
    • Any format needed?
  • How to collect it from other CEs, for other VOs?
    • Suggestion welcome!
  • Discussions to be started by email