A pre-configured anomaly detection job is supplied as part of the ML plugin for APM transaction data. This configuration is used inside the APM UI for adding anomaly detection to a specific environment e.g. staging or prod, with the APM UI adding metadata and an additional service.environment filter term to the datafeed query. These extra properties are not added when creating the APM transaction job from within the ML job wizard, and the APM UI displays the following warning:
We should add a warning inside the ML job wizard to recommend that the user creates the jobs inside the APM UI, for example by adding warning text inside the module description which is displayed in the pre-configured job card.
A pre-configured anomaly detection job is supplied as part of the ML plugin for APM transaction data. This configuration is used inside the APM UI for adding anomaly detection to a specific environment e.g. staging or prod, with the APM UI adding metadata and an additional
service.environment
filter term to the datafeed query. These extra properties are not added when creating the APM transaction job from within the ML job wizard, and the APM UI displays the following warning:We should add a warning inside the ML job wizard to recommend that the user creates the jobs inside the APM UI, for example by adding warning text inside the module description which is displayed in the pre-configured job card.