2020-11-18 Reval Legacy/Old GMC Sync

Date	18 Nov 2020
Authors
Status	Resolved
Summary	Ran the GMC SYNC ETL and INTREPID REVAL ETLs (`intrepid-reval-etl` and `intrepid-reval-etl-all-prod`) We didn't bother adding monitoring to the existing sync jobs as new revalidation is soon going to be live Do need to add monitoring to sync jobs and ETLs for new revalidation - https://hee-tis.atlassian.net/browse/TISNEW-3264
Impact

Non-technical summary

18 Nov 2020 -09:48 AM
18 Nov 2020 - 10:25 AM	Created ticket and incident page https://hee-tis.atlassian.net/browse/TISNEW-5728 2020-11-18 Reval Legacy/Old GMC Sync
18 Nov 2020 - Between 10:25 and 11:21	Ran the jobs `intrepid-reval-etl` and `intrepid-reval-etl-all-prod` Fixed the refresh of data but difference between the under notice values between TIS legacy/existing reval and GMC Connect
18 Nov 2020 12:06	Ran the GMC Sync and intrepid-reval-etl-all-prod again via Jenkins
18 Nov 2020 12:25	Seems to be fixed

User reported in Teams Support Channel that their connections had not been working correctly

Running of the Sync, intrepid-reval-etl and intrepid-reval-etl-all-prod jobs

For new reval - we need add monitoring so we know if the sync jobs and ETLS are run successfully or fail - https://hee-tis.atlassian.net/browse/TISNEW-3264

Still limited knowledge within the existing teams about how the existing module exists
Need monitoring - we raised this on August 22, 2019 and still have not done it
Jobs need to be run via Jenkins
intrepid-reval-etl builds the ETL?