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.

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

[Stack Monitoring] migrate elasticsearch node overview page to React #113318

Merged
merged 2 commits into from
Sep 29, 2021

Conversation

neptunian
Copy link
Contributor

@neptunian neptunian commented Sep 28, 2021

#113339
#112822

Migrates Elasticsearch -> Nodes -> Overview page

  • Breadcrumbs will not be correct as its being done separately
  • The tab menu is not correct and I will implement it when migrating the Nodes -> Advanced view . In this PR it continues to use the Nodes view menu. This is what it will look like after updated:
    Screen Shot 2021-09-28 at 1 43 08 PM
  • Instead of using the existing React components which have angular functionality embedded in them i created new components of the same name appended with "React" which can be removed when "Angular mode" is no longer needed.

Test

  • Access the page by going to Elasticsearch Nodes listing. Click on one of the nodes (pick one with shards):

Screen Shot 2021-09-28 at 6 36 22 PM

  • Make sure the page updates with new data when it auto refreshes (I used Edge to get some data)
  • Clicking on "Filter for system indices" under Shard Legend to hide or show system indices should work update correctly
  • make sure you can drag and zoom into the charts

@neptunian neptunian self-assigned this Sep 28, 2021
interface ParsedMonitoringData {
[key: string]: any;
}
export const useLocalStorage = <Value>(key: string, defaultValue: Value): [Value, Function] => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@neptunian
Copy link
Contributor Author

@elasticmachine merge upstream

Copy link
Contributor

@matschaffer matschaffer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks solid to me on docker-test-cluster. It has the same brush/url update issue I've seen on other graphs, but #112063 should address that.

@neptunian neptunian added auto-backport Deprecated - use backport:version if exact versions are needed Feature:Stack Monitoring labels Sep 29, 2021
@neptunian neptunian merged commit 682a1c1 into elastic:master Sep 29, 2021
kibanamachine added a commit to kibanamachine/kibana that referenced this pull request Sep 29, 2021
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

💚 Backport successful

Status Branch Result
7.x

This backport PR will be merged automatically after passing CI.

neptunian added a commit to neptunian/kibana that referenced this pull request Sep 29, 2021
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
monitoring 607 614 +7

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
monitoring 953.1KB 972.3KB +19.2KB

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @neptunian

neptunian added a commit that referenced this pull request Sep 29, 2021
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed Epic: Stack Monitoring de-angularization Feature:Stack Monitoring release_note:skip Skip the PR/issue when compiling release notes v7.16.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants