Logging response headers from New Relic endpoint to DEBUG logs.

[vuqtran88]

Feature Description

When we send data up to New Relic, the response headers that we get back from New Relic have been useful for debugging issues like missing data due to 503s, it's useful to know if the issues were isolated to a particular geo-location. Additionally, if the failure is Cloudflare related, Cloudflare is going to need a ray ID and request ID to debug these issues.

Currently, for the .NET agent, we only logged the response body.

Priority:
Low - Nice to have (visited 9/13/2022)

[nrcventura]

I don't think that audit logs is the right place for this information. I think adding them to the DEBUG level agent logs would be more appropriate, which is where we are already logging the response body.

[vuqtran88]

I have changed the title.

[github-actions]

This Issue has been marked stale after 90 days with no activity. It will be closed in 30 days if there is no activity.

[angelatan2]

12/10/2021 The .NET agent may need to support this feature as it is in the x-agent spec.