Project

General

Profile

Feature #20234

Report failure of a POMS campaign submission in the offline dashboard of experiments.

Added by Anna Mazzacane over 1 year ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
06/27/2018
Due date:
% Done:

100%

Estimated time:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

I have already mentioned this to Steve and Marc.
This request come from the uBooNE offline checklist where the offline shifters has to look at POMS campaign submissions and report if there are failures in the latest 24hours.
The offline dashboard for uBooNE is https://landscape.fnal.gov/monitor/d/HMj5hqVik/production-shifter?orgId=1&var-vo=uboone.
In this dashboard there is the list of POMS campaigns (ACTIVE?). If there is a failure, could the campaign be marked in red?

This could be useful also for other experiments.

(The idea is that poms would check its log file, for each submission, and send something to fifemon indicating if the submission worked or failed. Then the shifter report could be updated to show red for those where the submission failed. ---- Steve)

Associated revisions

Revision cae51f44 (diff)
Added by Marc Mengel about 1 year ago

Draft of change for issue #20234

History

#1 Updated by Anna Mazzacane over 1 year ago

  • Subject changed from Report into the offline dashboard if a campaign submission failed. to Report failure of a POMS campaign submission in the offline dashboard of experiments.

#2 Updated by Stephen White over 1 year ago

  • Target version set to v4_1_0

#3 Updated by Stephen White over 1 year ago

  • Description updated (diff)
  • Assignee set to Marc Mengel

#4 Updated by Marc Mengel about 1 year ago

So, I chatted with kretzke in slack; he says we can:

```curl -XPOST https://landscape.fnal.gov/ingest/my-data/_doc -d '{"foo":"bar","baz":"qux"}'```

we just need to know what `my-data` is and expected field types

So I'm going to look at reporting in the slurp_jobid script in poms_jobsub_wrapper.

It will have been reading the output of jobsub_submit, so we should be able to tell if we got a jobid back or not.

#5 Updated by Marc Mengel about 1 year ago

Changes are in cae51f444353 and 67595b45c61

we collect up some lines from the jobsub output and report them to elasticsearch under poms_jobsub, then we'll be able to get them included (we hope) in the dashboards, etc.

#6 Updated by Marc Mengel about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#7 Updated by Stephen White 12 months ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF