2018-12-08
Sergii Gladchenko Ops Team
Complete, resolved
The customer data was not sent from AES EDI. The investigation showed that the file with the data was sent, but it did not get processed due to an issue with the AES CIS service.
About 486,000 records were affected and the EDI to CIS monitoring service too.
Sending a big record's file at the same time of the running of the patching script caused a wreck in the data processing.
A large amount of files were not processed.
Reloading the AES CIS monitoring service allowed us to spot the missed records that were not discovered automatically.
Our customer create this Jira to alert us on this failure. Please refer to (AESEDI-53447)
| Action Item | Type | Owner | Bug |
|---|---|---|---|
| Writing of monitoring policy to detect records missings | prevent | LMP | DONE |
| Monitor the data ingesters and processors (ETL) | prevent | LMP | (Jira Issue No: AESCIS-38263)TODO |
We have to add more monitoring plugins and modules to watch this critical part of our infrastructure.
2018-12-08 (all times UTC)
| Time | Description |
|---|---|
| 11:56 | Discovering of the missing files |
| 12:00 | Restarting of the AES CIS monitoring module |
| 12:15 | Starting of the data processing of the records files |
| 13:00 | Completion of the data processing of all the 486,000 records files |