-
Notifications
You must be signed in to change notification settings - Fork 213
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create IVC-Forms-Monitor-Incident.md
New template for IVC Forms team
- Loading branch information
1 parent
e08fedc
commit c4c2510
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
name: IVC Forms Monitor Incident | ||
about: IVC Forms team template for tickets that result from monitoring | ||
title: 'IVC Forms: <Date> Monitor Incident - <Description>' | ||
labels: 'ivc-forms, monitoring' | ||
assignees: '' | ||
project: IVC Forms | ||
--- | ||
|
||
Per [playbook](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/champva/team/ivc-forms-monitoring-playbook.md), opening ticket to track details of this [**LINK TO DD MONITOR ALERT IN SLACK**]. | ||
Slack discussion [**LINK TO SLACK DISCUSSION IF SEPARATE FROM ABOVE] | ||
|
||
|
||
**Intake** | ||
- [ ] PM (Bo) and DM (Andrea) have been notified | ||
- [ ] PM and DM confirmation of ticket creation | ||
- [ ] Incident ticket linked to sprint monitoring ticket [**LINK HERE TOO?] | ||
|
||
**Investigation** | ||
- [ ] Verify that vets-api is receiving submits from vets-website | ||
- [ ] Verify that files are sent successfully to s3 | ||
- [ ] Verify that the callback API is available | ||
- [ ] Determine whether the issue arose due to a deployment, either by the IVC Forms team or the PEGA team. | ||
- [ ] IVC | ||
- [ ] If root cause has been identified as an issue in vets-website or vets-api, notify PM and DM to determine next stpes with PO | ||
- [ ] PEGA | ||
- [ ] If root cause has been identified as an issue outside of vets-website and vets-api, work with the PM, DM, and PO to determine contacts and next steps. | ||
|
||
**Resolution** | ||
- [ ] Acknowledge monitoring alerts in slack | ||
- [ ] IVC Forms engineering will provide updates on development and deployment of a solution and its status in each environment | ||
- [ ] IVC Forms engineering will notify PM and DM when resolved | ||
- [ ] IVC Forms engineering will monitor outstanding missing statuses and ensure they are cleared appropriately. No statuses should be deleted or cleared without agreement from PO and or PM | ||
- [ ] If traffic to the site has been altered, PO or PM will determine when to return to previous levels. |