mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
f51ac13197
## Summary Updates the navigation for Machine Learning pages, moving admin tasks for managing ML jobs and models to a single place inside Stack Management, and leaving exploratory tasks in a consolidated top-level Machine Learning menu. The available items vary by solution, so that the navigation for an Elasticsearch project, for example, contains a single item for managing trained models. #### Stack management menu for classic/observability/security nav <img width="275" alt="Screenshot 2025-04-04 at 16 10 04" src="https://github.com/user-attachments/assets/14b6e8d4-7111-4fbd-ae5d-9f389f83f23c" /> #### Stack management for search: <img width="271" alt="Screenshot 2025-04-07 at 14 38 45" src="https://github.com/user-attachments/assets/e104bf20-8a4d-4eed-9b5b-9c05944091ca" /> #### Machine Learning menu for Classic nav <img width="341" alt="Screenshot 2025-04-07 at 14 22 03" src="https://github.com/user-attachments/assets/610efd59-311f-410f-9881-548359ca7997" /> #### Machine Learning menu for Observability <img width="522" alt="Screenshot 2025-04-04 at 16 11 48" src="https://github.com/user-attachments/assets/ef16acf1-4d39-4494-a5d3-0fb078d74730" /> #### Machine Learning menu for Security <img width="528" alt="Screenshot 2025-04-04 at 17 46 43" src="https://github.com/user-attachments/assets/2df20c20-b894-4421-a732-9370bb5d6f2d" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] 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 - [ ] 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 was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Quynh Nguyen <quynh.nguyen@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Timothy Sullivan <tsullivan@elastic.co> |
||
|---|---|---|
| .. | ||
| kibana.yml | ||
| node.options | ||
| README.md | ||
| serverless.chat.yml | ||
| serverless.es.yml | ||
| serverless.oblt.yml | ||
| serverless.security.complete.yml | ||
| serverless.security.essentials.yml | ||
| serverless.security.search_ai_lake.yml | ||
| serverless.security.yml | ||
| serverless.yml | ||
as work on serverless picks up we will add config values to these files that
define how Kibana will run in "serverless" modes. To start Kibana locally with
this configuration, pass --serverless={mode} or run yarn serverless-{mode}
valid modes are currently: es, oblt, security and chat
configuration is applied in the following order, later values override
- serverless.yml (serverless configs go first)
- serverless.{mode}.yml (serverless configs go first)
- base config, in this preference order:
- my-config.yml(s) (set by --config)
- env-config.yml (described by
env.KBN_CONFIG_PATHS) - kibana.yml (default @
env.KBN_PATH_CONF/kibana.yml)
- kibana.dev.yml
- serverless.dev.yml
- serverless.{mode}.dev.yml