As an engineer I want to have Sentry be available in cloud.gov

[andrew-jameson]

Description: As follow-on for #831 , we will need to implement our backend performance monitoring solution.

Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue

• [ ] Sentry application exists in prod cloud.gov space
• [ ] Sentry application can view all spaces/environments with granularity
• [ ] Sentry application is on by default for local dev environments
• [ ] Testing Checklist has been run and all tests pass
• [ ] README is updated, if necessary

Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

• [ ] Ensure deployment logic accounts for new Sentry docker image(s) both bash and circleCI
• [ ] Create infrastructure-as-code Sentry configuration(s)/image(s)
• [ ] Prop up intra-space nginx routing
• [ ] Ensure cloud.gov resources are allocated well
• [ ] Run Testing Checklist and confirm all tests pass

Notes:

• In testing, Sentry used 4GB but may use more across multiple environments.

Supporting Documentation:

Open Questions:

• Can we use multiple docker images in ClamAV node? [ STRETCH GOAL ]
• We may be able to piggy-back off ClamAV and run multiple images in one node