Generate log tarball URL in ElasticSearch ads

[bbockelm]

For production jobs, we currently store the tarballs in CMS EOS (and they are readable by CMS members).

The URL can be constructed with the following recipe:

"https://eoscmsweb.cern.ch/eos/cms/store/logs/prod/recent/" + \
   <task name> + "/" + \
   <step name> + "/" + \
   <schedd name> + <WMAgent job ID> + "-" + <retry #> + "-log.tar.gz"

For WMAgent jobs, can we add a new attribute (LogURL?) containing a URL constructed as above?

[stiegerb]

I just tried this out for a single document, but I didn't manage. E.g. this one:
https://es-cms.cern.ch/kibana/app/kibana#/doc/AWgsoJKc-0N6utS00NKf/cms-2019-04-05/job?id=vocms0281.cern.ch%2339053.7%231554422724%231554468823&_g=()

• Task name (from WMAgent_SubTaskName) is: /pdmvserv_task_HIG-RunIIFall17wmLHEGS-03605__v1_T_190328_123738_3923/HIG-RunIIFall17wmLHEGS-03605_0
• Schedd is vocms0281.cern.ch (from ScheddName)
• WMAgent job ID is 3758522 (from WMAgent_JobID)
• Retry # is 0 (from CMS_JobRetryCount)

How do I get the step name?

[bbockelm]

Sorry - it’s request name, not task name. The step name is going to be the last piece of the path of the full task name. I think it might be stored as a separate attribute?