Closed FranECross closed 2 weeks ago
Because Github markup / styling has changed and it's harder to see now: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/19353 was cut, as a follow up of this ticket.
Reviewed Bryan's notes, and we have the follow up ticket in current sprint. Closing.
Description
The following features needs to be evaluated to determine if it meets the standards for 'zero silent failures', which is a user-facing transaction that is submitted to the back-end system. For the two below, search terms are sent to the Search.gov API. If we identify any missing monitoring, etc. from evaluating the checklist, we will file tickets to update implementation.
OCTODE guidance states:
Problem Statement:
Artifacts
User story
AS A I WANT SO THAT
Engineering notes / background
If you need to set up monitoring in DataDog:
Set up monitoring in Datadog
Follow this guidance on endpoint monitoring to get going. Then following the guidance on monitoring performance to get up to speed with Datadog.
Examples
Additional examples
Analytics considerations
Quality / testing notes
Acceptance criteria
Checklist
Start
Around 6 years ago the original search was introduced and has been built upon since
No, it has been recently adjusted to move from an API directly on search.gov to an identical one provided at gsa.gov. This was done per the search providers recommendation and is an identical endpoint. User data is not being captured/lost with this change.
Monitoring
Yes, monitored in multiple ways here
Yes all monitoring has the appropriate required tags at minimum
Yes, errors from monitors alert the #public-websites-dd-search channel in slack
Yes, the Sitewide team follows this channel which currently has 15 members
Yes, Sitewide has monitors assigned weekly who watch the channel more actively to investigate errors that occur and connect with the appropriate VFS teams to help resolve if a solution can't be introduced through git
⚠️ Failure to have endpoint monitoring in place is a blocking QA standard at Staging review as of 9/10/24. If you answered no to any of the questions above, you will be blocked from shipping at the Staging review touchpoint in Collab Cycle.
Reporting errors
Documentation
The API interactions include a GET request to the vets-api that utilizes a search.gov API GET request to generate the results. The possible error will be returned as HTTP errors
User experience
[x] Do you capture all of the potential points of failure and make those errors known to the user via email notification and/or through the application on VA.gov or the mobile application?
[x] Create a user data flow diagram
Learn how to create a user data flow diagram
File silent errors issues in Github
We don't have any silent errors!
Great! Please let us know that you went through the checklist above as a team and did not find any silent failures in our Slack channel: #zero-silent-failures. You don't have to hang out in there once you have notified us. Just pop in, tell us who you are (which team and in which portfolio) and that no failures were found. Thanks!