Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Date

Authors

Joseph (Pepe) Kelly

Status

Summary

We received loads of sentry errors

Impact

Non-technical Description

We have a {Lambda} that follows changes in the revalidation database and it keeps track of what the most recent change processed was. The reference to that latest change couldn’t be used.???Because…???

We moved the old reference and made a change to the code to enable the {Lambda} to restart tracking changes.it

Since Saturday morning until Monday morning the changes in the Reval Database could not be reflected on Reval UI .

Trigger

  • There were a lot of Sentry errors at about 2,800 unclear whether anything was missed?


Detection


Resolution


Timeline

All times in GMT unless indicated

  • 05:29 - Earliest Slack message identifying an issue with the production CDC Lambda

  • ~06:00 - renamed attribute in the database collection. This caused other issues which were resolved by applying a hotfix to generate a new reference.

  • -

  • -

Root Cause(s)


Action Items

Action Items

Owner


Lessons Learned

  • No labels