[Monitoring] Migrate server to NP

[chrisronline]

This PR migrates the stack monitoring server code to the new platform!

TODO

• Adopt core metrics service (once officially ready): Add core metrics service #58623

[chrisronline]

@elasticmachine merge upstream

[elasticmachine]

merge conflict between base and head

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: a924775

History

• 💔 Build #24766 failed 16234d5
• 💔 Build #24732 failed a07810f
• 💔 Build #24724 failed 6bf8c29
• 💔 Build #24674 failed d1ac0cb
• 💔 Build #24374 failed 14037d8

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

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[chrisronline]

@elasticmachine merge upstream

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: ffd807d

History

• 💔 Build #25097 failed a924775
• 💔 Build #24766 failed 16234d5
• 💔 Build #24732 failed a07810f
• 💔 Build #24724 failed 6bf8c29
• 💔 Build #24674 failed d1ac0cb

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

[chrisronline]

@elasticmachine merge upstream

[elasticmachine]

merge conflict between base and head

[chrisronline]

CI blocked by #56872

[mshustov]

@chrisronline #57655 landed. you should be able to reuse elasticsearh config as

import {ElasticsearchConfig} from 'src/core/server';
const config$ = config.create().pipe(map(rawConfig => new ElasticsearchConfig(rawConfig)));
const client$ = config$.pipe(map(config => elasticsearch.createClient('monitoring', config));

In this case, hosts will be wrapped in an array --> createClient merges configs correctly.

[peteharverson]

@chrisronline spotted the CI error from the ML job cloning test on this PR. If you haven't done so already, you probably want to rebase against master as we disabled this test yesterday whilst we work on a stability fix for the failing test.

[chrisronline]

@elasticmachine merge upstream

[igoristic]

I’m kinda confused about why we still need x-pack/legacy/plugins/monitoring/config.js? Won't it be replaced by x-pack/plugins/monitoring/server/config.ts

Or will it be gone when we do the complete cutover to NP?

[igoristic]

Awesome job @chrisronline 🏆 🎉 💯 Loving the progressive Typescript take over 💝

[chrisronline]

Or will it be gone when we do the complete cutover to NP?

Yea, it should be gone when we completely switch over. It's still there because the client side code reads from it too.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 492761b

History

• 💚 Build #34236 succeeded 64560e7
• 💔 Build #34182 failed 6340e5d
• 💚 Build #33540 succeeded b719600
• 💚 Build #33110 succeeded 28e288e
• 💚 Build #33057 succeeded 863b326

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

[chrisronline]

Backport:

7.x: 8d9f39b

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 56675 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 56675 or prevent reminders by adding the backport:skip label.

[chrisronline]

I did backport this @kibanamachine. You okay?