-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Remove additional "No data" message and re-ordering charts #75399
Merged
cauemarcondes
merged 19 commits into
elastic:master
from
cauemarcondes:apm-chart-remove-msg
Sep 1, 2020
Merged
Changes from 11 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
624b2a3
removing extra message
cauemarcondes 37410ce
adding x-axis values when no data is available
cauemarcondes 6cef87d
reordering charts
cauemarcondes 37b5c47
fixing internationalization
cauemarcondes c713db9
fixing transaction RUM agent order
cauemarcondes 1868699
Merge branch 'master' of github.com:elastic/kibana into apm-chart-rem…
cauemarcondes 31ac18d
addressing PR comment
cauemarcondes 911e4bd
Merge branch 'master' into apm-chart-remove-msg
elasticmachine 263fdce
removing kpis list and show it in the chart legend instead
cauemarcondes 2f907f1
fixing API test
cauemarcondes 3eb4f5f
Merge branch 'master' into apm-chart-remove-msg
elasticmachine 2caea0c
Merge branch 'master' into apm-chart-remove-msg
elasticmachine eae5696
Merge branch 'master' into apm-chart-remove-msg
elasticmachine a807f06
moving asPercent to the common directory
cauemarcondes 799e1fb
fixing api test
cauemarcondes 5ab6936
Merge branch 'master' of github.com:elastic/kibana into apm-chart-rem…
cauemarcondes d960841
fixing unit test
cauemarcondes 04bfdd0
removing unused prop
cauemarcondes c4f5968
fixing unit test
cauemarcondes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
75 changes: 0 additions & 75 deletions
75
...plugins/apm/public/components/shared/TransactionBreakdown/TransactionBreakdownKpiList.tsx
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason for overwriting series here, and not where it's defined?
kibana/x-pack/plugins/apm/server/lib/transactions/breakdown/index.ts
Lines 211 to 217 in 63265b6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
asPercent
is defined in/public
and I think the server doesn't have to know how the UI is going to show the value, it should only provide the value. I have my concerns aboutcolor
,type
andhideLegend
, maybe they should all be removed from the server and be defined only in the client.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #70161 in the backlog.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It depends. Are there any drawbacks to defining it on the server? I see clear drawbacks in defining the chart config across multiple files.
That being said, if it's too much of a hassle because it'll require you to move
asPercent
and its dependencies to the server I'm fine with leaving it as-is.@smith Regarding #70161: I'd be surprised if we don't have a way to access the advanced settings from the server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your input @sqren, the only drawback I can see here is that I'd have to move the
asPercent
to a common place. But if it makes sense the server to send the value already formatted then I wouldn't think it as a drawback but as an improvement. My question is does it make sense sending the value already formatted from the server? For what I've seen we never send any formatted value from the server, we always leave this responsibility to the client.FYI: I'm not against moving the
asPercent
, I only want to keep consistency across all APIs we've got.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smith: why? (Other than it being the convention)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On a technical level, some explanation is in #70161. If a users are using different themes and the API includes the colors of the lines the API would have to return different responses based on the theme.
If the presentational elements are coupled with the chart data, changing the presentation becomes more difficult.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For theming then it makes sense, although I can imagine that can be supported on the server as well. Personally I'm not swayed by "presentational data belongs on the client". IME, server-side code is more predictable and testable, and it's nice to have it in one place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, for now then I'll move the
asPercent
to the common directory and return the value already formatted from the server. We can continue discussing on Nathan's issue #70161.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good @cauemarcondes 👍