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.

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

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

Open
kaylareopelle opened this issue Jan 6, 2025 · 1 comment
Labels

Comments

@kaylareopelle
Copy link
Contributor

kaylareopelle commented Jan 6, 2025

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.

@workato-integration
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant