-
Notifications
You must be signed in to change notification settings - Fork 6.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
Machine View Sorting / Grouping #9214
Merged
Merged
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
3fa2569
Convert NodeInfo.tsx to a functional component
51bb292
Update NodeRowGroup to be a functional component
8ae204e
lint
265dc75
Convert TotalRow to functional component.
bd899fe
lint
9da701d
move node info over to using the sortable table head component. spaci…
fef027e
Factor a NoewWorkerRow class out of NodeRowGroup that will be usable …
16e1d51
Compilation checkpoint, I factored the worker filtering logic out of …
5d10acc
Add sort accessors for CPU
feb2d18
Add sort accessors for Disk
8934430
Add sort accessors for RAM
7493992
add a table sort util for function based accessors (rather than flat …
2bfa0d3
wip refactor node info features
bef05fe
wip
edae34f
Rendering Checkpoint. I've refactored the features and how they are c…
0d4c423
wip
69608fa
wip
c34a2e7
wip
f7898bb
Finish adding sorting and grouping of machine view
bdb9502
Merge branch 'master' into machine-view-sort-group
4b99a42
lint
a106d86
Merge branch 'master' into machine-view-sort-group
20c9e09
fix bug in filtration of logs and errors by worker from recent refactor.
92fb224
Merge branch 'master' into machine-view-sort-group
f64d92b
Add export of Cluster Disk feature
b00d42b
Merge branch 'master' into machine-view-sort-group
mfitton 581f490
fix some merge issues
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
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.
Why do we stop collecting this per IP? How do we distinguish logs from same pids in different machines?
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.
Good question. The log entries by IP used to be a top level attribute, so the response looked like
where each client in clients represents one IP.
Now, the log_count and error_count exists on a per-client level, so each client has a
log_counts
anderror_counts
that corresponds to its IP. This simplifies the logic on the front-end a lot, since trying to refactor the log and error features to work with theNodeFeatures
andWorkerFeatures
arguments would have been difficult otherwise.This was changed on the backend accordingly.