Notes around work that is happening, if applicable (optional, please delete if unused)
Tasks
[ ] What things need to happen?
Acceptance Criteria
[ ] What are the specific things that must be true in order for this to be accepted?
Reminders
[ ] Please attach your team label and any other appropriate label(s) (operations, devops, and needs-grooming will automatically be applied as part of the template)
[ ] Please connect to an epic (this will typically be done by the Platform Operations PM or TL)
Description
This is a placeholder issue that acts as a reminder to check back with the Lighthouse Infrastructure team to see if the latency of the
fhir
component is more stable. As part of https://github.com/department-of-veterans-affairs/va.gov-team/issues/43859, it was determined thatfhir
was dragging down overall site latency. It was removed from the pager duty alert in https://github.com/department-of-veterans-affairs/devops/pull/12018 and a Temp alert was created. We should bring it back into the main Site Latency alert.I'm not exactly sure what needs to be done here, if anything.
Background/context
lighthouse-infrastructure slack thread: https://dsva.slack.com/archives/C013VCQKSE7/p1663599625846669
Technical notes
Notes around work that is happening, if applicable (optional, please delete if unused)
Tasks
Acceptance Criteria
Reminders