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

Apdex for a transaction should be marked as "frustrating" if an error is present, regardless of the transaction time #2104

Open
jtduffy opened this issue Oct 23, 2024 · 1 comment
Open

Apdex for a transaction should be marked as "frustrating" if an error is present, regardless of the transaction time #2104

jtduffy opened this issue Oct 23, 2024 · 1 comment
Labels
oct-dec qtr Represents proposed work item for the Oct-Dec quarter

Comments

@jtduffy
Copy link
Contributor

jtduffy commented Oct 23, 2024

When an error occurs during a web request, the agent is properly incrementing the frustrating counter, which will be reflected in the overall apdex score for the application. However, the transaction specific apdex can still be marked as satisfied if the transaction time is small enough.

The agent spec seems to imply that the transaction apdex should be marked as frustrating (since the associated metric is incremented). Will need to discuss with other agent teams.
@jtduffy jtduffy added the oct-dec qtr Represents proposed work item for the Oct-Dec quarter label Oct 23, 2024
@workato-integration
Copy link

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

@jtduffy jtduffy changed the title Apdex for a transaction should be marked as "frustrating" if an error is present, regardless of the transactoin time Apdex for a transaction should be marked as "frustrating" if an error is present, regardless of the transaction time Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
oct-dec qtr Represents proposed work item for the Oct-Dec quarter
Projects
Java Engineering Board
Status: Triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jtduffy