Enable Toxic Exposure 1.1 25% traffic

[pacerwow]

This ticket allocates Sprint effort for the 50% Toxic Exposure release. It includes the responsibilities of Release Monitoring, which is coordinated by the team. Typically, this is one person who assumes this responsibility for the sprint.

Tasks

• [ ] Each Friday before EST COB, share application health metrics for the previous week relative to the release with OCTO, including any baseline metrics that are applicable
• [ ] Share application health metrics as needed ad hoc, as this may sometimes be necessary
• [ ] Make any necessary changes to our monitoring, alerting, and dashboards to accurately monitor the release and respond to any stakeholder questions
• [ ] Perform manual remediation when necessary
• [ ] Update Release Monitoring documentation, or other documentation as needed - be proactive
• [ ] Respond to Slack messages as needed
• [ ] The next business day after the team has incremented to 100%, help gather release metrics
• [ ] update release increment metrics here: Monitoring Toxic Exposure Release
• [ ] @pacerwow GA4 to report form metrics (especially opt-in, form exit, and abandonment)

Release Monitor Playbook

Playbook

references

• Toxic Exposure Submission Troubleshooting
• Team 1 526 Submission Remediation Playbook

Metrics

Baseline EVSS submissions from April 1 to July 31 209,770 total submissions (primary, backup, and failure) 99.04% used the primary path (207,772) 0.94% used the backup path (1,959) 0.00019% completely failed (4)

Toxic Exposure Toxic Exposure N% incremental rollout (Date 1 - Date 2): Lighthouse total submissions: N

Primary Path Submissions N% used the Lighthouse primary path (2,993)

Backup Path Submissions N% used the Lighthouse backup path (68)

Failures N% of Lighthouse submissions failed (14)

Technical Notes: Here, add notes about technical fixes, issues we're experiencing, details for remediating them

Next Steps: Next steps for the release, including details on anything mentioned in Technical Notes

## Acceptance Criteria

• [ ] You've done due diligence to make sure that the team has the information they need to continue with the release and ensure OCTO's questions are answered in a timely manner
• [ ] Documentation and processes are updated so that the next Release Monitor's job is easier

Additional Information

The team should @ mention the Release Monitor so that managing Slack threads is trivial for them. Keeping conversations organized in a thread will help reduce the cognitive load of managing the release.

[mchae-nava]

Note to self that this period ends on the 12th, and to generate the report then