Failed to get job configs to include in ML usage

Failed to get job configs to include in ML usage – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.17-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve the configurations for Machine Learning (ML) jobs. This could be due to issues with the ML module, incorrect permissions, or network connectivity problems. To resolve this, you can check if the ML module is properly installed and enabled. Also, ensure that the user has the necessary permissions to access the ML jobs. Lastly, verify your network connections and settings. If the issue persists, consider checking the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Failed to get job configs to include in ML usage ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Failed to get job configs to include in ML usage” classname is MachineLearningUsageTransportAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        ActionListener jobStatsListener = ActionListener.wrap(
            response -> jobManagerHolder.getJobManager().expandJobs(Metadata.ALL; true; ActionListener.wrap(jobs -> {
                addJobsUsage(response; jobs.results(); jobsUsage);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);
            }; e -> {
                logger.warn("Failed to get job configs to include in ML usage"; e);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);
            }));
            e -> {
                logger.warn("Failed to get job stats to include in ML usage"; e);
                client.execute(GetDatafeedsStatsAction.INSTANCE; datafeedStatsRequest; datafeedStatsListener);