SoT: Monitoring

[jadudm]

Problem

Is there a diff in the data?

Submission ───────► SAC ────────► Dissemination────► API 1.1.0
     │                                                        
     │                                                        
     └───────────► SoT ─────────► API 2.0

How did we discover this problem?

Job Story(s)

When I [situation], I want to [motivation] so I can [outcome/benefit].

What are we planning to do about it?

What are we not planning to do about it?

How will we measure success?

Security Considerations

Required per CM-4.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

[jadudm]

Possibilities (conversation w/ JP):

• Modify save() on models to check?
• Daily check between SAC/SoT?
• Add an Admin API endpoint to let us inspect the live tables?
• Database trigger? (Similar to modifying save(), but at a lower level...)
  • But... no idea where it would log to, because of Cloud.gov

Either way, the question is "how do we know things are consistent between the two models while things are in flight, as opposed to after they are done?"

[jperson1]

Bonus tasks carried on from #4619:

1. Move Alerts (related to slack integration) into terraform. Combine metrics from the endpoint monitoring dashboards with alerts.
2. Add API information to NewRelic.