Kibana: [APM] Service maps fails to load, displays errors when there are no ML jobs for apm

[ogupte]

Service maps is failing to load because it doesn’t handle the case where there are no ML jobs for APM. The request for 'apm' ml jobs throws with a 404, and is caught at the router level, returning a 500 error for the service maps api call. This should be handled by returning an empty anomalies array instead of throwing.

One workaround is to enable ML anomaly detection on at least 1 service in APM. Another is to disable ML entirely in kibana.yml with xpack.ml.enabled: false

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[sqren]

@ogupte How severe is this? Is the service map not usable for people without ML integration?

[ogupte]

Anomaly detection has the same license requirements as service maps, so they should be able to do the workaround to view service maps. If something prevents the user from creating an APM ml job, then service maps will be broken until the patch release with the bug fix.

[sqren]

This is going to surprise a lot of users. And while the workaround is easy to do it's not at all obvious. We'll most likely get some support tickets about this so we should make sure the right people know about this (eg. support).

[bmorelli25]

Added to Kibana's known issues in https://github.com/elastic/kibana/pull/69435.