Skip to content

Understand why request.uri and other agent attributes on Transactions are not ingested into New Relic #3008

Open
@kaylareopelle

Description

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, the request.uri attribute was present in the agentAttributes payload. This behavior can be reproduced on a minimal Rails application.

In addition, request.parameters.id was also dropped. However, other request.* parameters, like request.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.

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions