Batch Importer (Bib/Acq)
(UXPROD-47)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | R1 2021 | Parent: | Batch Importer (Bib/Acq) |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Khalilah Gambrell |
| Resolution: | Done | Votes: | 0 |
| Labels: | data-import | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Release: | R1 2021 Hot FIx #2 | ||||||||||||||||||||||||||||
| Epic Link: | Batch Importer (Bib/Acq) | ||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||
| Description |
|
Update: Approved as R1 2021 Hot Fix at Capacity Planning Team meeting on May 17, 2021. If there isn't time, this will be included in Juniper. Requirement
NOTE: Alert e-mails would go to hosting providers for live libraries, or library staff for self-hosted, or TBD for hosted ref envs and Bugfest Other questions/topics from 20200421 Folijet standup:
Week of 26 April: Oleksii Kuzminov will arrange for Folijet and Spitfire to meet with Vladimir Shalaev to decide on a strategy and create stories. Discuss with Khalilah Gambrell and Ann-Marie Breaux and confirm team(s) by the end of the week. |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 14/May/21 ] |
|
Discussed with Khalilah Gambrell and decided to turn this into a feature, assigned to Spitfire. Copied the spike details into the description, and linked the stories to it. Also created a task to account for additional work that will govern the notifications |
| Comment by Khalilah Gambrell [ 17/May/21 ] |
|
Goal is to have this work complete by Hotfix Iris Release #2 but can push to Juniper. |
| Comment by Mike Gorrell [ 25/May/21 ] |
|
Will this health check be accessible via an API so that we may call it from our existing monitoring tools/processes? Will there be any granularity in what is flagged as a problem - i.e. "stuck job" vs "nothing running" ? |
| Comment by Vladimir Shalaev [ 25/May/21 ] |
|
This is a message in a log like "Job XXX seems to be stuck". It has no recover mechanism (thou we can add it with relative ease - send another message if the job previously notified gets back to life). So in general it's a 'signal', which can be parsed and reacted by any monitoring toolset |