Improve application performance, experience for March

[jadudm]

Story

March is a significant submission deadline. Our goal, through the month of February and March, is to be ready for the heavy season at the end of the month.

What follows are ideas we might develop into tickets to tackle on short(er) order. Some might be too large to undertake. Some might want to be thrown out, or rewritten. This ticket wants to be discussed and shaped before breaking out any individual tasks. The spirit here is "we need the FAC to be performant before March 15th."

Ideas

Beta Give feedback

1. Rotate everyone on the team through the helpdesk
2. Update cluster names and ALN lists/program names to be current/correct
3. Fix the broken workflow where auditees certify but do not submit
4. Review, improve documentation for everything users encounter difficulty with.
5. Load test the FAC in a performance-like condition (e.g. multiple instances in staging)
6. Normalize our DB, application infrastructure across all environments
7. Provide standard (large) data testing sets for developers to use locally
8. Automate data loading into dev, staging for performance testing
9. Make observability part of all critical paths, verify common user stories/problems can be seen in NR

Possibly related tickets

Beta Give feedback

1. Investigate testing parity between deployed instances #3014
   debt eng +2
2. Update app navigation to match the static site #2814
   2 of 2
   eng +1
   
3. Implement Digital Analytics Program (DAP) for the FAC application and static site #2813
   3 of 3
   eng +1
   
4. [bug] Log out action redirects to the previous page instead of a general landing page, causing an unexpected 500 #2780
   bug cx eng +3
5. Create how-do-i-resubmit article for static site #2756
   3 of 4
   content cx +2
6. fac.gov / app.fac.gov do not appear in the DAP data #2229
   eng +1
7. FAC - Feature: use a second ClamAV instance for redundancy #3195
   eng infrastructure +2
   

   
8. Add support for multiple ClamAV instances #3455
   eng +1
   
9. Make ClamAV scanning performance visible in NewRelic #3456
   eng +1
   

[danswick]

This epic has become entangled with #3388.

[danswick]

March has come and gone. The straggling tickets here are still on the primary board, but we don't need to track this epic anymore.