Sustainable Kibana Architecture: Move modules owned by @elastic/stack-monitoring

[gsoldevila]

Summary

This PR aims at relocating some of the Kibana modules (plugins and packages) into a new folder structure, according to the Sustainable Kibana Architecture initiative.

Important

• We kindly ask you to:
  • Manually fix the errors in the error section below (if there are any).
  • Search for the packages[\/\\] and plugins[\/\\] patterns in the source code (Babel and Eslint config files), and update them appropriately.
  • Manually review .buildkite/scripts/pipelines/pull_request/pipeline.ts to ensure that any CI pipeline customizations continue to be correctly applied after the changed path names
  • Review all of the updated files, specially the .ts and .js files listed in the sections below, as some of them contain relative paths that have been updated.
  • Think of potential impact of the move, including tooling and configuration files that can be pointing to the relocated modules. E.g.:
    • customised eslint rules
    • docs pointing to source code

Note

• This PR has been auto-generated.
• Any manual contributions will be lost if the 'relocate' script is re-run.
• Try to obtain the missing reviews / approvals before applying manual fixes, and/or keep your changes in a .patch / git stash.
• Please use #sustainable_kibana_architecture Slack channel for feedback.

Are you trying to rebase this PR to solve merge conflicts? Please follow the steps describe here.

2 plugin(s) are going to be relocated:

Id	Target folder
@kbn/monitoring-collection-plugin	x-pack/platform/plugins/private/monitoring_collection
@kbn/monitoring-plugin	x-pack/platform/plugins/private/monitoring

Updated relative paths

x-pack/platform/plugins/private/monitoring/dev_docs/how_to/testing.md:7
x-pack/platform/plugins/private/monitoring/dev_docs/how_to/testing.md:8
x-pack/platform/plugins/private/monitoring/jest.config.js:10
x-pack/platform/plugins/private/monitoring/tsconfig.json:2
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:100
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:103
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:106
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:109
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:115
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:121
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:127
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:130
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:133
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:136
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:139
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:142
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:145
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:19
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:2
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:22
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:25
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:28
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:31
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:34
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:37
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:64
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:67
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:70
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:73
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:76
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:79
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:82
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:85
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:88
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:91
x-pack/platform/plugins/private/monitoring/tsconfig.type_check.json:97
x-pack/platform/plugins/private/monitoring_collection/jest.config.js:10
x-pack/platform/plugins/private/monitoring_collection/tsconfig.json:2
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:16
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:19
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:2
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:22
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:25
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:28
x-pack/platform/plugins/private/monitoring_collection/tsconfig.type_check.json:31

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[andreadelrio]

*.scss files renamed without changes.

[pickypg]

It looks like there was a copy/paste error that added the /solutions/observability path twice almost everywhere in files. I added it everywhere I caught it so that you could do it in a single batch. Alternatively, feel free to just do a find/replace in your local branch.

[gbamparop]

@gsoldevila there are some open PRs to categorise monitoring as a platform plugin:

• [Stack Monitoring] Remove 'observability' and 'observabilityShared' plugin dependencies #203492
• Remove dependency on infra in monitoring plugin #203551

Would it be possible to update this PR once they are merged, as there wouldn't be a need to move it to the observability folder?

[gbamparop]

@gsoldevila the PRs were merged, monitoring is now a platform plugin, sorry about the inconvenience.

[gbamparop]

Thanks! The code paths are correct, I haven't tested the app.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: eead556
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #262840 failed 7e8880b
• 💚 Build #261861 succeeded c832358
• 💛 Build #259456 was flaky 3c93bad
• 💚 Build #258877 succeeded 6043706
• 💔 Build #258391 failed 8530e0e

[pgayvallet]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation