You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The New Relic SDK specification defines functionality to append field-values to the User-Agent header. Exporters need to use this functionality to include information about what systems they are instrumenting. This is critical to ensuring analytics about data sources are possible.
The specification should have a section providing guidelines about how this field is formed and what valid values include. At a minimum values need to conform to the product definitions defined in RFC 7231 Section 5.5.3. Additionally, values should likely be required to include information about the instrumented systems in some encouraged format.
The text was updated successfully, but these errors were encountered:
Initial thoughts on what the guidelines should be changed to include:
SHOULD append a product identifier for the instrumented system. (going with SHOULD here to allow for the end user to deliberately override the decision).
MUST use the functionality offered by the SDK to append the User-Agent header. (don’t want the exporter overriding the SDK portion of the header).
The New Relic SDK specification defines functionality to append field-values to the
User-Agent
header. Exporters need to use this functionality to include information about what systems they are instrumenting. This is critical to ensuring analytics about data sources are possible.The specification should have a section providing guidelines about how this field is formed and what valid values include. At a minimum values need to conform to the
product
definitions defined in RFC 7231 Section 5.5.3. Additionally, values should likely be required to include information about the instrumented systems in some encouraged format.The text was updated successfully, but these errors were encountered: