Include HTTP headers with all Transactions #1029
Assignees
Labels
2
Story Point Estimate
community
To tag external issues and PRs submitted by the community
feature request
To tag feature request after Hero Triage for PM to disposition
Milestone
Comments
jamesarosen
added
the
feature request
github-actions
bot
added
the
community
|
Hello @jamesarosen |
|
Hi @jamesarosen thanks for the suggestion. We try and maintain feature parity with our agents and several agents have implemented support for capturing HTTP headers. We will add this to our backlog. |
|
Let's size this story and then assess next steps. |
angelatan2
removed
the
feature request
angelatan2
added
the
feature request
|
Link to ticket where we worked on logging HTTP headers: #1839 |
kford-newrelic
added
2
fallwith
added a commit
that referenced
this issue
Aug 9, 2023
A new 'allow_all_headers' configuration parameter has been added to bring parity with the Node.js agent and others. This configuration parameter defaults to a value of `false`. When set to `true` and as long as the agent is not operating in high security mode, all HTTP headers gleaned from a request will be captured and relayed to New Relic instead of the default core set of headers. All existing behavior for `.*attributes.include` and `.*attributes.exclude` configuration parameters will be respected for any desired filtration of the headers when `allow_all_headers` is enabled. This work was done in response to a feature request submitted by community member [@jamesarosen](https://github.com/jamesarosen). Thank you very much, @jamesarosen! resolves #1029
|
Hi @jamesarosen, thanks again for suggesting this feature! The PR to introduce a new |
|
Nice work, team 👏 |
|
Version 9.4.0 of the agent is now available from RubyGems.org. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Yes? The Ruby agent lacks features that the JS agent has, so we're missing data.
Feature Description
The Node JS agent supports sending all HTTP headers via the
allow_all_headersflag. This results in attributes likerequest.headers.acceptshowing up as attributes on all Transactions. See New Relic Data Dictionary for more on those attributes.Describe Alternatives
We can add each header as a custom attribute. This works fine, but it's a fair bit of extra code we have to maintain.
Priority
Really Want
T-Shirt size
The text was updated successfully, but these errors were encountered: