Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
Concorde - Sprint 97, Concorde - Sprint 98
-
3
-
Concorde
Description
Purpose/Overview:
Create API so that UI can retrieve error log and render it to the user.
Requirements/Scope:
1. Errors should be grouped by export job id
2. Errors should contain following elements:
- date, time
- log level (set to ERROR in Q3)
- reason
- affected record - if applicable
Additional information:
1.Type of errors tracked:
- Underlying data (missing required data, invalid/duplicate keys, null or empty values, too long/large values)
- Connectivity issue (no response from db, S3)
- Creating export file (Storage space)
- Reading input file (UUID not found, invalid data, cannot find the file for reading, file not found)
- Mappings (null or empty, too long/large value, unsupported mapping)
Link to MindMap file: https://drive.google.com/file/d/1WLc1YvhwTL4pAiTBpBsiGMAj5mxBJE3x/view?usp=sharing
2. Details of affected records are tracked in MDEXP-257 (Instances), MDEXP-259 (Holdings), MDEXP-260 (Items)
Approach:
Create an API GET/data-export/logs/
. Come up with a schema to handle all the above types of errors.
Acceptance criteria:
- Come up with the schema to handle all the above scenarios
- API is created
- Unit and API tests are written
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2326 Export Manager - logs details
-
- Closed
-
- has to be done before
-
MDEXP-259 Log errors for Holdings records export
-
- Closed
-
-
MDEXP-260 Log errors for Inventory Item records export
-
- Closed
-
-
UIDEXP-144 Render error log details
-
- Closed
-
- relates to
-
MDEXP-625 Report affected instance when export contains negative number of failed records
-
- In Code Review
-