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.

Sign up for GitHub

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

Jump to bottom

Java agent uses apdexPerfZone instead of nr.apdexPerfZone on Transaction events #2196

Open
kmudduluru opened this issue Jan 10, 2025 · 1 comment
Open

Java agent uses apdexPerfZone instead of nr.apdexPerfZone on Transaction events #2196

kmudduluru opened this issue Jan 10, 2025 · 1 comment
Labels
1 Story Point Estimate jan-mar qtr Represents proposed work item for the Jan-Mar quarter
Milestone
Java Agent - FY25...

Comments

@kmudduluru
Copy link

kmudduluru commented Jan 10, 2025 •
edited
Loading

Related jira ticket -
https://new-relic.atlassian.net/browse/NR-346144

Java apps use add a apdexPerfZone attribute on Transaction events, and Node/.NET/Ruby apps are all using a non-customer facing attribute nr.apdexPerfZone.
Should send both attributes - nr.apdexPerfZone , apdexPerfZone on transaction events to match with other agents.
@kmudduluru kmudduluru moved this to Next Quarter Candidates in Java Engineering Board Jan 10, 2025
@workato-integration
Copy link

https://new-relic.atlassian.net/browse/NR-357515

@kmudduluru kmudduluru added the jan-mar qtr Represents proposed work item for the Jan-Mar quarter label Jan 10, 2025
@kmudduluru kmudduluru added the 1 Story Point Estimate label Jan 16, 2025
@kmudduluru kmudduluru moved this from Next Quarter Candidates to In Quarter in Java Engineering Board Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 Story Point Estimate jan-mar qtr Represents proposed work item for the Jan-Mar quarter
Projects
Java Engineering Board
Status: In Quarter
Milestone
Java Agent - FY25Q4 KTLO & Instrument...
Development

No branches or pull requests
1 participant
@kmudduluru