Create list of Platform Product-owned integrations to prevent silent failures

[jennb33]

User Story

As the managers and developers of the VA Platform, We need create a list of the list of integration managed within the VA system, So that we know what endpoints will have to be watched for silent failures.

Issue Description

After the work for endpoints discovery is complete, we need to compile the list of endpoints that we need to monitor so that silent failures are eliminated.

Tasks

• [ ] Create list of the integrations that are the responsibility of the Platform team and send to Clint for review with Jeff.
• [ ] Document all findings as above and link documentation either here or in comments

Success Metrics

The Platform Product team will be aware of the integrations that are to be monitored to ensure against any silent failures.

Acceptance Criteria

• [ ] We will have a list of integrations to monitor and ensure that there are no silent failures.

Notes

Please review this guidance document for background and how-to discovery. This document was supplied by Matt Dingee.

Reference this document for past endpoint-specific work from the eMIS migration.

---

Validation

Assignee to add steps to this section. List the actions that need to be taken to confirm this issue is complete. Include any necessary links or context. State the expected outcome.

[rmtolmach]

See vets-api CODEOWNERS for files exclusively owned by backend-review-group.

[rmtolmach]

Resource: https://vfs.atlassian.net/wiki/spaces/PPT/pages/3446341633/Discovery+Endpoint+Monitoring+Requirements#Platform-Owned-Endpoints