[APM] Creating ML Jobs from Integration Context Menu fails for different transaction types

[simioa]

Kibana version: 6.6.0 Elasticsearch version: 6.6.0 Server OS version: RHEL 7.5 Browser version: Chrome 71 Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): yum Describe the bug: Creating ML Jobs from Integration Context Menu for the same Service fails for different transaction types. Creation of second ML Job fails with message:

Your current license may not allow for creating machine learning jobs, or this job may already exist.

Steps to reproduce:

1. Have a APM Service with two or more Transaction Types
2. Create the first ML Job for the first transaction type using the Integrations Context Menu in APM (Integrations -> Enable anomaly detection -> Select the first transaction Type at the drop down menu -> Click "Create new Job")
3. Create the second ML Job for the second transaction type using the Integrations Context Menu in APM (Integrations -> Enable anomaly detection -> Select the second transaction Type at the drop down menu -> Click "Create new Job")

Expected behavior: The Creation of the ML Jobs should be successful for every Transaction Type Screenshots (if relevant):

[elasticmachine]

Pinging @elastic/ml-ui