-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] Change "response time" label to "duration" for all transaction types for all agents #24722
Comments
Pinging @elastic/apm-ui |
Would it be ok to just change it to "duration" across the board (and not check for "if request, keep as resp time")? Would be nice to reduce the complexity there and "duration" is always true, not sure it's necessary to treat one type special with wording? |
I believe we're going back and forth on whether to support more language-specific terminology in the UI. In my opinion, we're delivering a curated UI for the languages, and that means supporting the terminology that best fits the standards of that language. That wasn't so much a comment to choosing duration over response time for requests, which I think we could agree on, but especially the RUM agent has very specific transaction types that demands another terminology, so if we start in one place, we may already have to have a system in place to handle different units or terms for transactions for the different languages. Would like to know what @roncohen or @makwarth thinks about unification > customization when we're thinking about the user experience. |
I'm leaning towards "duration" for all languages. As long as the transaction type is clear (which I think it is atm), it will be quite clear what "duration" refers to. E.g. for RUM, you're on the "Page load times" tab and the chart title is "duration". |
@makwarth Ok, that sounds good. I'll update the description and title of this issue, so it's clear what needs to happen. |
Summary
We want to simplify the UI by changing the "response time" label (which actually only made sense for the transaction type "request") to "duration" for all transaction types for all agents. This means there's no differentiation to keep track of from different transaction types.
Tasks
Examples
Transactions list
Transaction detail page
The text was updated successfully, but these errors were encountered: