[Monitoring] Migrate Elasticsearch ML Jobs View from Angular

[Zacqary]

Summary

Closes #113646

Migrates the Elasticsearch/Machine Learning Jobs view to React.

This required me to create a new ElasticsearchMLJobs React component, as the Angular view uses its own unique directive for unclear reasons and didn't follow the standard of other views.

To test:

• Start Metricbeat
• Create at least one Machine Learning job (you can create 3 at a time using the very first Metricbeat option; try doing this twice to test pagination)
• Open the ML Jobs tab and ensure all functionality is the same when enabling/disabling monitoring.ui.render_react_app: true

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[matschaffer]

Testing (via docker-test-cluster)

Unsure if docker-test-cluster supports ML jobs. Will find out :)

• Start Metricbeat (create index pattern for it too)
• Create at least one Machine Learning job (you can create 3 at a time using the very first Metricbeat option; try doing this twice to test pagination)
• Open the ML Jobs tab and ensure all functionality is the same when enabling/disabling monitoring.ui.render_react_app: true

[matschaffer]

Gonna say this is good. I can't seem to get jobs to stay open so I think I'm missing a section of functionality. I'll start a cloud cluster and try the testing there to see if I can reach the node screens.

The angular app seems to lack pagination and throws console errors when sorting. So I'd say we're ahead of the game already.

[matschaffer]

Ah, if you connect to monitoring-oblt, then release-oblt has an ongoing job

Looks like the node link isn't getting populated correctly, just undefined

Found a bug! :)

[matschaffer]

See screenshot. Would probably be good to fix that first. Otherwise this looks awesome.

[Zacqary]

@matschaffer Turns out this bug also exists in the Angular version, so that's fun.

Should I try to fix it in this PR or just merge and open a new issue for it?

[neptunian]

If it exists in angular I think its fine to open a new PR unless you prefer to do it here.

[Zacqary]

@neptunian @matschaffer Actually turned out to be a relatively simple fix

Bug fixed, rest of PR approved

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e90ecd1
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
monitoring	647	650	+3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
monitoring	1.0MB	1.1MB	+7.1KB

History

• 💚 Build #158108 succeeded 920948c

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

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.