Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Logging response headers from New Relic endpoint to DEBUG logs. #112

Open
vuqtran88 opened this issue Aug 19, 2020 · 5 comments
Open

Logging response headers from New Relic endpoint to DEBUG logs. #112

vuqtran88 opened this issue Aug 19, 2020 · 5 comments
Labels
enhancement New feature or request technical debt

Comments

@vuqtran88
Copy link
Contributor

vuqtran88 commented Aug 19, 2020 •
edited by angelatan2
Loading

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
Copy link
Member

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 vuqtran88 changed the title Logging response headers from New Relic endpoint to audit logs. Logging response headers from New Relic endpoint to DEBUG logs. Aug 19, 2020
@vuqtran88 vuqtran88 added the enhancement New feature or request label Aug 19, 2020
@vuqtran88
Copy link
Contributor Author

I have changed the title.

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the stale label Nov 18, 2020
@angelatan2 angelatan2 added on-hold On hold pending more information and removed stale labels Nov 18, 2020
@angelatan2 angelatan2 added this to the FY22Q1 Feature Pack milestone Mar 2, 2021
@angelatan2 angelatan2 modified the milestones: FY22Q2 - Feature Pack, FY22Q3 - Feature Pack Jun 15, 2021
@elucus elucus modified the milestones: FY22Q3 - Feature Pack, FY22Q4 - Feature Pack Oct 11, 2021
@elucus elucus added the feature pack Flagged for consideration in an upcoming Feature Pack release label Nov 18, 2021
@angelatan2
Copy link
Contributor

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

@workato-integration
Copy link

workato-integration bot commented Sep 13, 2022 •
edited by nr-ahemsath
Loading

https://new-relic.atlassian.net/browse/NR-132421 (manually updated 2024-11-6 to the new JIRA location)

@angelatan2 angelatan2 added technical debt and removed feature pack Flagged for consideration in an upcoming Feature Pack release on-hold On hold pending more information labels Oct 19, 2022
@nr-ahemsath nr-ahemsath removed this from the FY23Q2 - Feature Pack milestone May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request technical debt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@elucus @nrcventura @vuqtran88 @nr-ahemsath @angelatan2