Prebuilt ML job for Heartbeat looks for no-more-existent dataset "uptime"

[herrBez]

Kibana version: 8.13.2

Elasticsearch version: 8.13.2

Server OS version: N/A (Elastic Cloud)

Browser version: (Google Chrome 124.0.6367.61 (Official Build) (64-bit))

Browser OS version: Windows 11

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Describe the bug:
The prebuilt ML job for Heartbeat uses the no-more-existent event.dataset called uptime. This dataset has been removed in the context of this PR in the Beats repository (release 7.15.0 of Heartbeat) and replaced with the monitor type tcp, http, icmp and browser.

Steps to reproduce:

1. Collect data with Heartbeat
2. Create a ML job on the Heartbeat dataset
3. Use the prebuilt Heartbeat ML job
4. Verify that the datastream does not start because there is no data matching event.dataset: "uptime"

Expected behavior:
The pre-built job should work with the data collected with modern version of Heartbeat too.
(Not sure but maybe we should have a type of job for each monitor type).

Screenshots (if relevant):

Errors in browser console (if relevant):

N/A

Provide logs and/or server output (if relevant):

N/A

Any additional context:

• Private slack discussion: https://elastic.slack.com/archives/CE4MRBU48/p1712816726385989

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[jasonrhodes]

@drewpost @paulb-elastic do you have any context on this and whether this ML job in Uptime is still something supported, regardless of the decisions around Uptime's future? I'm closing this as not priortized for us now but let me know if there are reasons to reassess.