* Fix calls to `/api/monitoring/v1/clusters` and `/api/monitoring/v1/elasticsearch_settings/check/cluster`
Seen on page: /app/monitoring
* Fix calls to `/api/index_management/indices/reload`
Seen on page: /app/kibana#/management/elasticsearch/index_management/indices
* Fix calls to `/api/cross_cluster_replication/follower_indices`
Seen on page: /app/kibana#/management/elasticsearch/cross_cluster_replication/follower_indices
* Fix calls to `/api/cross_cluster_replication/auto_follow_patterns`
Seen on page: /app/kibana#/management/elasticsearch/cross_cluster_replication/auto_follow_patterns
* Fix calls to `/api/remote_clusters`
Seen on page: /app/kibana#/management/elasticsearch/remote_clusters/list
* Fix calls to `/api/watcher/watches`
Seen on page: /app/kibana#/management/elasticsearch/watcher/watches
* Fix calls to `/api/rollup/jobs`
Seen on page: /app/kibana#/management/elasticsearch/rollup_jobs/job_list
* [Monitoring] Only do a single date_histogram agg for get_nodes calls (#43481)
* I think this is working now
* Add a way to uncovert, and then fix tests
* Remove unnecessary export
* Update snapshots
* normalize this across branches
* This is just interval in 6.8
* Switch the order of primaries and total in legend
* Revert "Switch the order of primaries and total in legend"
This reverts commit 895960af10.
* Reorder legend items
* Functional test fixes
* Added sorting to all columns
* Added sorting to table wrapper instead
* Fixed condition
* Removed default sorting value
* Removed a log statement
* Converted beats directive into a controller
* Minor changes to text.
* "Basic" is a proper name, so it should be capatalized.
* Cluster Alerts are plural.
* Fix tests to align with help text changes
* Missed one test file
* Protect against these fields not existing
* Add basic unit tests to ensure this behavior does not regress
* Expand this test to ensure we don't break on other pieces of data missing
* Use N/A if there is no value (rather than 0)
Resolves#27513.
_This PR is a combination of #31293 (the code changes) + #33570 (test updates). These two PRs were individually reviewed and merged into a feature branch. This combo PR here simply sets up the merge from the feature branch to `master`._
Summary of changes, taken from #31293:
The Logstash Pipeline Viewer UI would make a single Kibana API call to fetch all the information necessary to render the Logstash pipeline. This included information necessary to render the detail drawer that opens up when a user clicks on an individual vertex in the pipeline.
Naturally, this single API call fetched _a lot_ of data, not just from the Kibana server but also, in turn, from Elasticsearch as well. The "pro" of this approach was that the user would see instantaneous results if they clicked on a vertex in a pipeline and opened the detail drawer for that vertex. The "cons" were the amount of computation Elasticsearch had to perform and the amount of data being transferred over the wire between Elasticsearch and the Kibana server as well as between the Kibana server and the browser.
This PR makes the Kibana API call to fetch data necessary for **initially** rendering the pipeline — that is, with the detail drawer closed — much lighter. When the user clicks on a vertex in a pipeline, a second API call is then made to fetch data necessary for the detail drawer.
Based on a simple, 1-input, 1-filter, and 1-output pipeline.
* Before this PR, the Elasticsearch `logstash_stats` API responses (multiple calls were made using the `composite` aggregation over the `date_histogram` aggregation) generated a total of 1228 aggregation buckets (before any `filter_path`s were applied but across all `composite` "pages"). With this PR, the single `logstash_stats` API response (note that this is just for the initial rendering of the pipeline, with the detail drawer closed) generated 12 buckets (also before any `filter_path`s were applied). That's a **99.02% reduction** in number of buckets.
* Before this PR, the Elasticsearch `logstash_stats` API responses added up to 70319 bytes. With this PR, the single `logstash_stats` API response for the same pipeline is 746 bytes. That's a **98.93% reduction** in size.
* Before this PR, the Elasticsearch `logstash_state` API response was 7718 bytes. With this PR, the API response for the same pipeline is 2328 bytes. That's a **69.83% reduction** in size.
* Before this PR the Kibana API response was 51777 bytes. With this PR, the API response for the same pipeline is 2567 bytes (again, note that this is just for the initial rendering of the pipeline, with the detail drawer closed). That's a **95.04% reduction** in size.
* UI design touchup for 7.0
* clean up chart titles and beta icon
* Make shard list wrap on IE11
* wrap table cells with much content
* fix title height above graphs on ie11
* update tests and snapshots
* update functional test for node detail
* fixing more functional tests
* [deprecations] convert flattened settings to nested settings
* [deprecations] reuse rename method for elasticsearch.url to elasticsearch.hosts
* newline
* add known issues to docs
* [Monitoring] Fix issues with the localization effort (#29372)
* Fix issues with the localization effort, mainly due to two ongoing refactors in the same code
* Apply suggestions from code review
Co-Authored-By: chrisronline <chrisronline@gmail.com>
* PR feedback
* Fix broken test
* [Monitoring] Support for unlinked deployments (#28278)
* Unlinked deployment working for beats
* Use better constant
* Show N/A for license
* Rename to Unlinked Cluster
* Use callout to mention unlinked cluster
* PR feedback
* Use fragment
* Speed up the query by using terminate_after
* Handle failures more defensively
* Remove unnecessary msearch
* PR feedback
* PR feedback and a bit of light refactor
* Updated text
* Add api integration tests
* Localize call out
* Update loc pattern
* Fix improper i18n.translate usage
* Revert "Fix improper i18n.translate usage"
This reverts commit 0e2e7608c3.
* Revert "Update loc pattern"
This reverts commit cc99fe8a8a.
* Ensure the unlinked deployment cluster counts as a valid cluster
* Sometimes, you miss the smallest things
* Ensure the unlinked cluster is supported, in that users can click the link and load it
* Update tests
* PR feedback. Simplifying the flag supported code and adding more tests
* Update naming
* Rename to Standalone Cluster
* Remove unnecessary file
* Move logic for setting isSupported to exclusively in flag supported clusters code, update tests
* Fix up the data for these tests
* Updates react to 16.6 (latest)
* Updated fragment-based snapshots for Kibana root unit tests
* Updated fragment-based snapshots for x-pack unit tests
* Removed xpack yarn.lock file bc it is no longer needed, it was reintroduced by accident during a rebase in this branch
* React 16.6 snapshot updates, round 2 (mostly Fragment snapshot diffs)
* Updated last round of React 16.6 snapshots
* Fixes query bar issue with 16.4 gDSFP lifecycle
* Updated yarn lock (arraybuffer.slice updated)
* Updates snapshots where executeQueryOptions prop appears
* Move os info into OSS collection so the stats api can access it
* Fix tests
* copy this back for now
* Use server decorate to share from OSS to x-pack/plugins
* progress
* progress
* cleanup and elastic configs
* make upgrades to support adding aditional users, with
* use defaultDeep to ensure settings pass correctly
* move needed configs to start servers into kbn_server (except x-pack plugin paths and users)
* move xpack config to an export
* add more time
* diff rollbacks
* roll back prettier diff
* revert setupUsers signature
* remove more bluebird
* update bluebird for fixes with jest compatability
* fix ts errors
* dont allow jest to keep going making errors confising
* Separates configs for jest integration core/x-pack.
* Pass nested kbn config parameters.
* Adds example x-pack integration test using live es.
* Cloud detectors should be configurable for tests.
* Cloud detectors should use native promises only.
* No erroneous comments...
* Util is only for promisify, duh!
* New tests should have docuementation to help those looking to utilize them.
* Doc section headings should be consistent with each other.
* With git there is no need to commit commented code.
