Versions Compared

Old Version 4

changes.mady.by.user Philip Wilsdon

Saved on

compared with

New Version 5

changes.mady.by.user Philip Wilsdon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Authors

Status

Working on it

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

Table of Contents

Non-technical summary

Timeline

-09:48 AM

Image Modified

- 10:25 AM

Created ticket and incident page https://hee-tis.atlassian.net/browse/TISNEW-5728

2020-11-18 Reval Legacy/Old GMC Sync

- 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

Image Modified

12:06

Ran the GMC Sync and intrepid-reval-etl-all-prod  again via Jenkins

12:25

Seems to be fixed

Image Added

Root Causes

  • ???

Trigger

  • User reported in Teams Support Channel

Resolution

  • Running of the jobs intrepid-reval-etl and intrepid-reval-etl-all-prod

Detection

  • User reported in Teams Support Channel

Actions

  • For new reval - we

...

Lessons Learned (Good and Bad)

...

  • 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?