Attempt to install New Relic infrastructure agent

[btylerburton]

User Story

In order to monitor our system more effectively, @GSA/data-gov-team wants to attempt to install the NR Infrastructure agent.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN [a contextual precondition]
  [AND optionally another precondition]
  WHEN [a triggering event] happens
  THEN [a verifiable outcome]
  [AND optionally another verifiable outcome]

Background

After speaking with NR support on 9.27.23, we determined that we had configured the NR agent at the app level but not at the container level. We have doubts as to whether this is possible due to the K8s cluster being abstracted away from us by cloud.gov, but we plan to follow the NR tutorial they provided and see what's possible.

Security Considerations (required)

Ensure that the agent is not exfiltrating information to sites other than NR to the best of our ability.

Sketch

• Follow instructions on NR site (link)
• Attempt to install without Cloud.gov support
• Contact cloud.gov support if we can't do it by ourselves

[robert-bryson]

According to the docs, should be working with PRs: #4500 and GSA/catalog.data.gov#1111

Cannot test until first PR is merged and New Relic is allowed through the egress proxy.

[robert-bryson]

I have been having an issue with my machine's docker environment due something with the datagov-deploy redirects happening in the Dockerfile for postgres. Should be fixed with GSA/catalog.data.gov#1143. Thanks James for your help on this.

Should be back on track to being able to debug the NR connectivity issues.