Understand why request.uri
and other agent attributes on Transactions are not ingested into New Relic
#3008
Labels
request.uri
and other agent attributes on Transactions are not ingested into New Relic
#3008
An internal user of the New Relic Ruby agent discovered the
request.uri
agent attribute not available on transactions queried in the New Relic UI. After looking at the agent's audit logs for the same transaction, therequest.uri
attribute was present in theagentAttributes
payload. This behavior can be reproduced on a minimal Rails application.In addition,
request.parameters.id
was also dropped. However, otherrequest.*
parameters, likerequest.headers.accept
were preserved.This behavior does not seem to be consistent across all language agents and some other languages are accurately ingesting the
request.uri
attribute.Investigate the problem with internal teams to determine where in the ingest process the attribute is dropped.
See initial thread (internal) for details.
The text was updated successfully, but these errors were encountered: