Kibana: [APM] Service maps: test 5: user loads service maps without anomaly detection integration when xpack.ml.enabled: false

[cauemarcondes]

Clicking on Anomaly detection to enable ML with the plugin disabled (xpack.ml.enabled: false) breaks APM page.

[elasticmachine]

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

[sqren]

Thanks for testing this @cauemarcondes ! Was this part of the test plan? If not, please add it. Additionally, can you also add a line to check if there are no available ml nodes? It's something like xpack.ml.node (can't remember exactly)

[cauemarcondes]

Was this part of the test plan?

Yes, it was.

Additionally, can you also add a line to check if there are no available ml nodes? It's something like xpack.ml.node

WIll check what's the exact name and add in the test plan.

[jgowdyelastic]

ML has its own capabilities endpoint and shared function to use to check if it is enabled:
/api/ml/ml_capabilities or mlCapabilities in mlSystemProvider
we have an open issue to add the node count to that response:
https://github.com/elastic/kibana/issues/67412

For now you can call /api/ml/ml_node_count to get this count.
if you need it as a shared function for calling server side, I can add it.

[sqren]

@jgowdyelastic Thanks for chiming in! What I would like is a test case where we intentionally disable the ML node and then see how the ui behaves. I seem to recall there is an kibana.yml config option but can't remember what it's called.

[sqren]

@cauemarcondes / @ogupte Did you find a way to disable the ML node via kibana.yml or similar?

[cauemarcondes]

@cauemarcondes / @ogupte Did you find a way to disable the ML node via kibana.yml or similar?

Actually no, the discussion ended up here https://github.com/elastic/kibana/issues/72914#issuecomment-662978026

[sqren]

Okay, since this is a real (ish) problem (I ran into it on Elastic Cloud I think) it would be nice to know how to simulate and see how the ui behaves.

[jgowdyelastic]

Actually no, the discussion ended up here #72914 (comment)

Apologies, I don't think I saw this.
It's possible to disable ML on the node by adding node.ml: false in the elasticsearch.yml file.

[sqren]

It's possible to disable ML on the node by adding node.ml: false in the elasticsearch.yml file.

Great! I think that's what I was looking for!

@cauemarcondes : I think you can test this with the apm-integration-testing command

scripts/compose.py start master --elasticsearch-java-opts="node.ml=false"