Data views content mgmt with abstractions #16
Conversation
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
elastic#157735) ## Summary [Security] Defend Workflows team owns the security_solution_endpoint tests ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
This Pr is a follow up of [PR#157008](elastic#157008) and [PR#157147](elastic#157147). Changes: 1. Replaced usage of `euiThemeVars` by `useEuiTheme` and `useEuiFontSize`. 2. e2e cloudId following [cloud plugin format](https://github.com/elastic/kibana/tree/main/x-pack/plugins/cloud#cloudid).
…elastic#157710) Resolves elastic#156856 ## Summary Adds a default value to `aggType` and `groupBy` fields ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Adds the 8.8 docs for Kibana Global Settings, including elastic#151631. Docs preview: https://kibana_157769.docs-preview.app.elstc.co/guide/en/kibana/master/advanced-options.html#kibana-global-settings-reference
…t_mgmt_with_abstractions
Filters are no longer being picked up by `useData` in the log pattern analysis flyout, this looks like it might be a race condition caused by the `useEffect` which loads the state data. This state data will never change while the flyout is open and so rather than using a initial render `useEffect` the state can be loaded and used when `aiopsListState` is initialized.
## Summary elastic/security-team#6393 This PR is to address the issue where the asset page for Vuln mgmt page is showing options for pages that hasn't been developed yet. The fix includes 1. Removing Dashboard and Rule options on Asset tab if integration is Vuln Mgmt 2. Updating the link for Findings to redirect users to Findings/Vulnerability instead of Findings/Configuration if integration is Vuln Mgmt 3. Update parent integration asset to include both Dropdown from Cloud Posture and Vulnerability Management **Definition of done** - [x] Show all relevant pages split by Cloud Posture and Vulnerability Management in the parent integration assets - [x] Show only vulnerabilitiy management findings link when viewing Vulnerability Management->Assets - [x] Make sure KSPM and CSPM shows the same links available today <img width="1667" alt="Screen Shot 2023-04-24 at 5 24 10 PM" src="https://user-images.githubusercontent.com/8703149/234144304-782cdd29-8d0a-42eb-a210-56423868b0f7.png"> <img width="1654" alt="Screen Shot 2023-04-25 at 11 32 24 AM" src="https://user-images.githubusercontent.com/8703149/234370092-383b29b2-0c29-4f7e-9fcd-29c53edd4f10.png">
## Summary This test has been skipped for 3 years and no specific team owns it. ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
elastic#157118) ## Summary Remove a complex type of object that was used to pass around config settings, that was in place to follow code patterns from the old Kibana platform. Addresses https://github.com/elastic/kibana/pull/155081/files#r1188025616 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] Ensure hostname `0.0.0.0` is re-written to `localhost` and warning logs are working correctly ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Regression in `xpack.reporting.kibanaServer` yml settings | Low | Med | Reporting sometimes needs a URL to the Kibana server. The necessary protocol/hostname/port needed build the URL is sourced from kibana.yml settings under `server.*`, but can be overridden using settings in `xpack.reporting.kibanaServer`. This feature exists because the headless Chromium browser sometimes must connect to a proxy that Kibana otherwise doesn't know about. | ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
…eated by users (elastic#155699) Resolves: elastic#154581 This PR adds 'user-managed' label next to the API key owner name when the API key is created by the user. <img width="813" alt="Screenshot 2023-05-06 at 19 02 08" src="https://user-images.githubusercontent.com/92688503/236637767-d0c0ee00-1314-4824-b97a-b7bdf1b7f43b.png">
) ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. Currently, after navigating any page after the first page and clicking on vulnerability, the flyout displays incorrect details. Currently, we use the `data.page`, which lists the maximum amount of vulnerabilities(500 vulnerabilities). The `vulnerabilityIndex` is set each time, a user clicks to expand vulnerability. We were currently only selecting vulnerabilities from the first page. Solution: Use `slicedPage` to get the vulnerabilities on the current page and then select vulnerability by `vulnerabilityIndex` https://github.com/elastic/kibana/assets/17135495/df682ecf-d024-45e4-84ca-d7df22a60ec4
- Remove duplicated text - Add cors specific example <img width="1170" alt="image" src="https://github.com/elastic/kibana/assets/17390745/70e783af-67a3-498f-800a-9c663b4c58f2"> <img width="1167" alt="image" src="https://github.com/elastic/kibana/assets/17390745/e9b45a02-d798-45de-8dc5-38ee395b1806">
…lastic#157771) ## Summary Fixes the path regex to allow /* and /** values, also fixed a null pointer in yaml editor. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
…lastic#157762) resolves elastic#156112 Change task manager logging on status errors from `warn` to `debug. Making this change as we recently changed from `debug` to `warn` in elastic#154045 . But this ended up too noisy, especially at Kibana startup.
## Summary `[email protected]` ⏩ `[email protected]` 🦴 The primary changes in this upgrade are around the deprecated `EuiLoadingContent` being removed in favor of `EuiSkeletonText`. - Most instances have been a [direct swap of usage](elastic@327626a), but [some replacements were a bit more opinionated](elastic@e6ceb36) as I saw them as potential to take advantage of `EuiSkeletonText`'s syntactical sugar and screen reader announcements for when state switches to loaded. --- ## [`79.0.1`](https://github.com/elastic/eui/tree/v79.0.1) **Bug fixes** - Fixed broken push `EuiFlyout` behavior ([elastic#6764](elastic/eui#6764)) ## [`79.0.0`](https://github.com/elastic/eui/tree/v79.0.0) - Updated all `EuiSkeleton` components with new props that allow for more control over screen reader live announcements: `announceLoadingStatus`, `announceLoadedStatus`, and `ariaLiveProps` ([elastic#6752](elastic/eui#6752)) - Improved keyboard accessibility in `EuiPageHeader` by ensuring the right side menu items come into focus from left to right. ([elastic#6753](elastic/eui#6753)) **Breaking changes** - Removed deprecated `EuiLoadingContent`. Use the `EuiSkeleton` components instead. ([elastic#6754](elastic/eui#6754)) ## [`78.0.0`](https://github.com/elastic/eui/tree/v78.0.0) - Improved the contrast ratio of `EuiCheckbox`, `EuiRadio`, and `EuiSwitch` in their unchecked states to meet WCAG AA guidelines. ([elastic#6729](elastic/eui#6729)) - Added React Testing Library `*ByTestSubject` custom commands to `within()`. RTL utilities can be imported from `@elastic/eui/lib/test/rtl`. ([elastic#6737](elastic/eui#6737)) - Updated `EuiAvatar` to support a new letter `casing` prop that allow customizing text capitalization ([elastic#6739](elastic/eui#6739)) - Updated `EuiFocusTrap` to support the `gapMode` prop configuration (now defaults to `padding`) ([elastic#6744](elastic/eui#6744)) **Bug fixes** - Fixed inconsistency in `EuiSearchBar`'s AND/OR semantics between DSL and query string generation ([elastic#6717](elastic/eui#6717)) - Fixed `EuiFieldNumber`'s native browser validity detection causing extra unnecessary rerenders ([elastic#6741](elastic/eui#6741)) - Fixed the `scrollLock` property on `EuiFocusTrap` (and other components using `EuiFocusTrap`, such as `EuiFlyout` and `EuiModal`) to no longer block scrolling on nested portalled content, such as combobox dropdowns ([elastic#6744](elastic/eui#6744)) **Breaking changes** - `EuiAvatar`s with the default `user` type will now default to capitalizing all initials in uppercase ([elastic#6739](elastic/eui#6739)) --------- Co-authored-by: Kibana Machine <[email protected]>
Fixes elastic#142865 ## Summary The user can set a path for local data storage through CLI or `kibana.yml`, but this setting was not implemented and the default `data` directory was being used. There are a few instances of hard coded `data/xxx` paths in the codebase for babel, ci and testing which are not applicable to production. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]>
…57434) ## Summary Updated the code owner entry for `x-pack/plugins/serverless_search` from `@elastic/appex-sharedux` to `@elastic/enterprise-search-frontend` The Enterprise Search team will be owning the development of the serverless search solution and we will need to be the ones reviewing PRs within the team.
## Summary Remove the unused kbn-alerts package ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]>
…astic#157307) ## Summary Addresses elastic#156600 (comment) > Let's think if there is a way to throw an error when core chrome api are called from invalid plugins (in this cases only the serverless plugin would be allowed. This PR can be a starting point for discussion on the behavior we really want. This PR has a simple goal to ensure that non-serverless plugins do not call the `chrome.projects` API. However, it's not complete security, as the compile-time error would be easy to override. cc @sebelga @Dosant @clintandrewhall --- --- ### Checklist Delete any items that are not applicable to this PR. - [x] Documentation was added for features that require explanation or tutorials Internal documentation: https://docs.google.com/document/d/1ew8KYl6ROs_V7jeIXgeP_C9YgkYK2IPtuceo6KVF_jE/edit# --------- Co-authored-by: Clint Andrew Hall <[email protected]>
## Summary - Updated the "Transforms" side navigation link to go to ingest pipelines stack management page. This link will eventually be updated to a new page in June, but this page is closer to whats needed for now. - Add the Indexing API to the side nav as a placeholder, but it links to the getting started page for now, this will also be a new page in June.
Fixing very minor issues in the Kibana dev docs that I found as I was getting bootstrapped: - fixing bad markdown syntax - adding first startup info (url + credentials)
## Summary Adds the 8.8 documentation for the following: - Enable report sharing: elastic#153429 Docs preview: https://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/reporting-getting-started.html - Random sampling feature: elastic#143221 Docs preview: https://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#improve-visualization-loading-time - Improve Ignore global filters UI: elastic#154441 and elastic#155280 Docs preview: https://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#add-annotations --------- Co-authored-by: Tim Sullivan <[email protected]>
…8166) ## Summary This PR filters in network-related fields to improve threat research context, improve telemetry on existing network-based rules, and allow us to provide additional malicious indicators with research publications. - Issue backref'd - OOB artifact backref'd - Stakeholders and legal engaged cc @terrancedejesus for context. ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Multiple Spaces—unexpected behavior in non-default Kibana Space. | Low | High | Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces. | | Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. | High | Low | Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure. | | Code should gracefully handle cases when feature X or plugin Y are disabled. | Medium | High | Unit tests will verify that any feature flag or plugin combination still results in our service operational. | | [See more potential risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) | ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
…le field types (elastic#158035) ## Summary We received feedback that the given example would result in errors, since it targets both [string](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-body-content) and [numeric](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-bytes) fields, so we've updated the example with something that won't result in an error, and updated the docs with a note that explains when/why these errors may occur. ### Checklist Delete any items that are not applicable to this PR. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] Any UI touched in this PR is usable by keyboard only (learn more about [keyboard accessibility](https://webaim.org/techniques/keyboard/)) - [ ] Any UI touched in this PR does not create any new axe failures (run axe in browser: [FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/), [Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)) - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This renders correctly on smaller devices using a responsive layout. (You can test this [in your browser](https://www.browserstack.com/guide/responsive-testing-on-local-server)) - [ ] This was checked for [cross-browser compatibility](https://www.elastic.co/support/matrix#matrix_browsers) ### Risk Matrix Delete this section if it is not applicable to this PR. Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release. When forming the risk matrix, consider some of the following examples and how they may potentially impact the change: | Risk | Probability | Severity | Mitigation/Notes | |---------------------------|-------------|----------|-------------------------| | Multiple Spaces—unexpected behavior in non-default Kibana Space. | Low | High | Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces. | | Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. | High | Low | Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure. | | Code should gracefully handle cases when feature X or plugin Y are disabled. | Medium | High | Unit tests will verify that any feature flag or plugin combination still results in our service operational. | | [See more potential risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) | ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: gchaps <[email protected]>
…58186) Partially addresses elastic#157756 ## Summary This PR makes the UI of the following Security apps disable-able for serverless: - Users - Roles - Role Mappings **How to test:** 1. Start Elasticsearch with `yarn es snapshot` and Kibana with yarn `serverless-{mode}` where `{mode}` can be `es`, `security`, or `oblt`. 2. Verify that the Users app is not accessible and its path (`management/security/users`) leads to the Stack Management landing page. 3. Verify that the Roles app is not accessible and its path (`management/security/roles`) leads to the Stack Management landing page. 4. Verify that the Role Mappings app is not accessible and its path (`management/security/role_mappings`) leads to the Stack Management landing page. Test the Security apps in regular (non-serverless) mode: 1. Start Elasticsearch with `yarn es snapshot` and Kibana with `yarn start`. 2. Verify that Users, Roles, and Role Mappings apps work as expected.
## Summary Adding Footer to the Serverless Search getting started page. - The Search UI button doesn't currently have a link - The Icons at the bottom of the footer have placeholder links that will need to be updated later. ## Screenshots <img width="1665" alt="image" src="https://github.com/elastic/kibana/assets/1972968/663643fd-1ace-484c-9e8b-fb3899b68d58">
…#158024) ## Summary * Select language clients in Overview page * Updated svg images with 128 px * 128 px https://github.com/elastic/kibana/assets/55930906/b46cfa6b-652e-4914-af88-2fbd892f54eb **Updated Screenshot : Select language with reduced image size and flex group** <img width="1728" alt="Screenshot 2023-05-18 at 10 50 50 AM" src="https://github.com/elastic/kibana/assets/55930906/42f8865e-20f0-41e4-9ce5-bb683031324f"> --------- Co-authored-by: kibanamachine <[email protected]>
… Index Connector UI (elastic#158102) Resolves elastic#155303 ## Summary Removes the refresh switch from the EX Index Connector UI Before: <img width="422" alt="Screenshot 2023-05-18 at 2 42 46 PM" src="https://github.com/elastic/kibana/assets/13104637/1a2e2ff4-5247-43f7-89ae-776a23be9e95"> After: <img width="410" alt="Screenshot 2023-05-18 at 2 50 09 PM" src="https://github.com/elastic/kibana/assets/13104637/2be21cc6-f128-44b5-bd53-cf6945c6f729"> No changes to the API so this is not a breaking change. Previously created Index Connectors should still work as before. ## To Verify **Verify previously created connectors can be updated** 1. Create an ES Index connector with refresh=true on `main` or in a previous version 2. Switch to this branch and verify the connector still loads and changes to the connector preserves the `refresh` value **Verify creating connector from UI** 1. On this branch, create an ES Index connector and verify that `refresh` is set to `false` **Verify creating connector from API** 1. On this branch, use the API to create an ES connector and verify you can successfully create one with either refresh set to `true` or `false` ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
…when trays are expanded (elastic#157777) ## Summary Fixes an issue where when an action detail is shown via an expanded tray item and the total number of items goes beyond the first page on the response actions history page/flyout, switching between pages while the tray is open breaks the page. - [x] fix paging with trays expanded on a flyout - [x] fix paging with trays expanded on a page - [x] ensure when the page is loaded with `?withOutputs=` with action ids from different sets of pages, table paging doesn't break when paged, and trays show open for the action ids in `?withOutputs=` URL param - tests: - [x] page navigation flyout/page view - [x] page reload with URL params (cypress) **flyout**  **page**  *page with URL load* - three actions are open on two different pages - we re-load page 2 with two open trays and then navigate to page 1 to see the third one open - also re-load page 1; we see the tray open, then navigate to page 2 to see the other two trays open.  ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
…157802) Closes elastic#154937 This PR includes the steps to install standalone elastic agent + reporting the status from bash script back to kibana.  --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Yngrid Coello <[email protected]> Co-authored-by: Yngrid Coello <[email protected]>
Co-authored-by: shahzad31 <[email protected]>
…lastic#157802)" This reverts commit 12401b2.
Adds versioning to all of the ML kibana APIs.
Versions are added to the server side routes and to the client side
functions which call the routes.
Makes some small refactors to ensure only the functions inside
`ml/public/application/services/ml_api_service/` are where the ML APIs
are called.
Updates external plugins which call ML APIs to add the new versioning.
Updates API tests to add the API version to the request headers.
Our one public API has been given the version `'2023-05-15'`, all of the
internal APIs have been given the version `'1'`.
**Public APIs:**
`/api/ml/saved_objects/sync`
**Internal APIS:**
`/internal/ml/alerting/preview`
`/internal/ml/annotations`
`/internal/ml/annotations/index`
`/internal/ml/annotations/delete/{annotationId}`
`/internal/ml/anomaly_detectors`
`/internal/ml/anomaly_detectors/{jobId}`
`/internal/ml/anomaly_detectors/_stats`
`/internal/ml/anomaly_detectors/{jobId}/_stats`
`/internal/ml/anomaly_detectors/{jobId}`
`/internal/ml/anomaly_detectors/{jobId}/_update`
`/internal/ml/anomaly_detectors/{jobId}/_open`
`/internal/ml/anomaly_detectors/{jobId}/_close`
`/internal/ml/anomaly_detectors/{jobId}/_reset`
`/internal/ml/anomaly_detectors/{jobId}`
`/internal/ml/anomaly_detectors/_validate/detector`
`/internal/ml/anomaly_detectors/{jobId}/_forecast`
`/internal/ml/anomaly_detectors/{jobId}/results/records`
`/internal/ml/anomaly_detectors/{jobId}/results/buckets/{timestamp?}`
`/internal/ml/anomaly_detectors/{jobId}/results/overall_buckets`
`/internal/ml/anomaly_detectors/{jobId}/results/categories/{categoryId}`
`/internal/ml/anomaly_detectors/{jobId}/model_snapshots`
`/internal/ml/anomaly_detectors/{jobId}/model_snapshots/{snapshotId}`
`/internal/ml/anomaly_detectors/{jobId}/model_snapshots/{snapshotId}/_update`
`/internal/ml/anomaly_detectors/{jobId}/model_snapshots/{snapshotId}`
`/internal/ml/calendars`
`/internal/ml/calendars/{calendarIds}`
`/internal/ml/calendars`
`/internal/ml/calendars/{calendarId}`
`/internal/ml/calendars/{calendarId}`
`/internal/ml/data_frame/analytics`
`/internal/ml/data_frame/analytics/{analyticsId}`
`/internal/ml/data_frame/analytics/_stats`
`/internal/ml/data_frame/analytics/{analyticsId}/_stats`
`/internal/ml/data_frame/analytics/{analyticsId}`
`/internal/ml/data_frame/_evaluate`
`/internal/ml/data_frame/analytics/_explain`
`/internal/ml/data_frame/analytics/{analyticsId}`
`/internal/ml/data_frame/analytics/{analyticsId}/_start`
`/internal/ml/data_frame/analytics/{analyticsId}/_stop`
`/internal/ml/data_frame/analytics/{analyticsId}/_update`
`/internal/ml/data_frame/analytics/{analyticsId}/messages`
`/internal/ml/data_frame/analytics/jobs_exist`
`/internal/ml/data_frame/analytics/map/{analyticsId}`
`/internal/ml/data_frame/analytics/new_job_caps/{indexPattern}`
`/internal/ml/data_frame/analytics/validate`
`/internal/ml/data_visualizer/get_field_histograms/{indexPattern}`
`/internal/ml/datafeeds`
`/internal/ml/datafeeds/{datafeedId}`
`/internal/ml/datafeeds/_stats`
`/internal/ml/datafeeds/{datafeedId}/_stats`
`/internal/ml/datafeeds/{datafeedId}`
`/internal/ml/datafeeds/{datafeedId}/_update`
`/internal/ml/datafeeds/{datafeedId}`
`/internal/ml/datafeeds/{datafeedId}/_start`
`/internal/ml/datafeeds/{datafeedId}/_stop`
`/internal/ml/datafeeds/{datafeedId}/_preview`
`/internal/ml/fields_service/field_cardinality`
`/internal/ml/fields_service/time_field_range`
`/internal/ml/filters`
`/internal/ml/filters/{filterId}`
`/internal/ml/filters`
`/internal/ml/filters/{filterId}`
`/internal/ml/filters/{filterId}`
`/internal/ml/filters/_stats`
`/internal/ml/indices/field_caps`
`/internal/ml/job_audit_messages/messages/{jobId}`
`/internal/ml/job_audit_messages/messages`
`/internal/ml/job_audit_messages/clear_messages`
`/internal/ml/jobs/force_start_datafeeds`
`/internal/ml/jobs/stop_datafeeds`
`/internal/ml/jobs/delete_jobs`
`/internal/ml/jobs/close_jobs`
`/internal/ml/jobs/reset_jobs`
`/internal/ml/jobs/force_stop_and_close_job`
`/internal/ml/jobs/jobs_summary`
`/internal/ml/jobs/jobs_with_geo`
`/internal/ml/jobs/jobs_with_time_range`
`/internal/ml/jobs/job_for_cloning`
`/internal/ml/jobs/jobs`
`/internal/ml/jobs/groups`
`/internal/ml/jobs/update_groups`
`/internal/ml/jobs/blocking_jobs_tasks`
`/internal/ml/jobs/jobs_exist`
`/internal/ml/jobs/new_job_caps/{indexPattern}`
`/internal/ml/jobs/new_job_line_chart`
`/internal/ml/jobs/new_job_population_chart`
`/internal/ml/jobs/all_jobs_and_group_ids`
`/internal/ml/jobs/look_back_progress`
`/internal/ml/jobs/categorization_field_examples`
`/internal/ml/jobs/top_categories`
`/internal/ml/jobs/datafeed_preview`
`/internal/ml/jobs/revert_model_snapshot`
`/internal/ml/jobs/bulk_create`
`/internal/ml/validate/estimate_bucket_span`
`/internal/ml/validate/calculate_model_memory_limit`
`/internal/ml/validate/cardinality`
`/internal/ml/validate/job`
`/internal/ml/validate/datafeed_preview`
`/internal/ml/json_schema`
`/internal/ml/management/list/{listType}`
`/internal/ml/model_management/nodes_overview`
`/internal/ml/model_management/memory_usage`
`/internal/ml/modules/recognize/{indexPatternTitle}`
`/internal/ml/modules/get_module/{moduleId?}`
`/internal/ml/modules/setup/{moduleId}`
`/internal/ml/modules/jobs_exist/{moduleId}`
`/internal/ml/notifications`
`/internal/ml/notifications/count`
`/internal/ml/results/anomalies_table_data`
`/internal/ml/results/category_definition`
`/internal/ml/results/max_anomaly_score`
`/internal/ml/results/category_examples`
`/internal/ml/results/partition_fields_values`
`/internal/ml/results/anomaly_search`
`/internal/ml/results/{jobId}/categorizer_stats`
`/internal/ml/results/category_stopped_partitions`
`/internal/ml/results/datafeed_results_chart`
`/internal/ml/results/anomaly_charts`
`/internal/ml/results/anomaly_records`
`/internal/ml/saved_objects/status`
`/internal/ml/saved_objects/initialize`
`/internal/ml/saved_objects/sync_check`
`/internal/ml/saved_objects/update_jobs_spaces`
`/internal/ml/saved_objects/update_trained_models_spaces`
`/internal/ml/saved_objects/remove_item_from_current_space`
`/internal/ml/saved_objects/jobs_spaces`
`/internal/ml/saved_objects/trained_models_spaces`
`/internal/ml/saved_objects/can_delete_ml_space_aware_item/{jobType}`
`/internal/ml/_has_privileges`
`/internal/ml/ml_capabilities`
`/internal/ml/ml_node_count`
`/internal/ml/info`
`/internal/ml/es_search`
`/internal/ml/index_exists`
`/internal/ml/trained_models/{modelId?}`
`/internal/ml/trained_models/_stats`
`/internal/ml/trained_models/{modelId}/_stats`
`/internal/ml/trained_models/{modelId}/pipelines`
`/internal/ml/trained_models/{modelId}`
`/internal/ml/trained_models/{modelId}`
`/internal/ml/trained_models/{modelId}/deployment/_start`
`/internal/ml/trained_models/{modelId}/{deploymentId}/deployment/_update`
`/internal/ml/trained_models/{modelId}/{deploymentId}/deployment/_stop`
`/internal/ml/trained_models/pipeline_simulate`
`/internal/ml/trained_models/infer/{modelId}/{deploymentId}`
## Summary This PR decodes the response returned by the user actions service. Depends on: elastic#157858, elastic#156622 ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [x] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]>
This adds steps to the [Install Kibana with Docker](https://www.elastic.co/guide/en/kibana/current/docker.html) page for verifying the downloaded Docker images. I split apart the original version which had all the commands in one block. Having them separate allows us to add in the optional "verify images" step with a link to the Elasticsearch docs for additional info. Rel: elastic/dev#2002 **Preview** ---  ---  --------- Co-authored-by: Tiago Costa <[email protected]>
…tic#157… (elastic#158325) Revert PR elastic#157659 due to blocking serverless image promotion.
…ation from Create Search App Flyout (elastic#158120) ## Summary * Remove search application name validation from UI side in Create search application Flyout, Instead verify error from logs. https://github.com/elastic/kibana/assets/55930906/2a945d8d-45ae-41ce-a143-a126b993132d
mattkime
pushed a commit
that referenced
this pull request
Oct 6, 2023
elastic#167877) Revert of elastic#164574 Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Xavier Mouligneau <[email protected]>
mattkime
pushed a commit
that referenced
this pull request
Nov 20, 2023
elastic#170411) …2282) (elastic#169580)" This reverts commit a382569.
mattkime
pushed a commit
that referenced
this pull request
Jan 9, 2024
…s-updated [Discover] Small fixes for types and memo deps. Add tests.
mattkime
pushed a commit
that referenced
this pull request
Sep 24, 2024
elastic#170432) …2282) (elastic#169581)" This reverts commit c8260c3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers