From c7dacd64c3aa8d725b24c3edb60f0b69bdfe59c2 Mon Sep 17 00:00:00 2001
From: Ryland Herrick <ryalnd@gmail.com>
Date: Wed, 28 Oct 2020 14:18:08 -0500
Subject: [PATCH] Fix regression in our ml usage collection

A regression was introduced in #74965 that caused an error to be
thrown while collecting telemetry on ML jobs. Because such exceptions
are caught and we degrade to zeroing out those counts, this one was not
caught until manual testing of telemetry.
---
 .../server/usage/detections/detections_helpers.ts               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x-pack/plugins/security_solution/server/usage/detections/detections_helpers.ts b/x-pack/plugins/security_solution/server/usage/detections/detections_helpers.ts
index 5cf17af2fa9c0b..6387839db3bfeb 100644
--- a/x-pack/plugins/security_solution/server/usage/detections/detections_helpers.ts
+++ b/x-pack/plugins/security_solution/server/usage/detections/detections_helpers.ts
@@ -172,7 +172,7 @@ export const getMlJobsUsage = async (ml: MlPluginSetup | undefined): Promise<MlJ
 
   if (ml) {
     try {
-      const fakeRequest = {} as KibanaRequest;
+      const fakeRequest = { headers: {} } as KibanaRequest;
       const fakeSOClient = {} as SavedObjectsClient;
 
       const modules = await ml.modulesProvider(fakeRequest, fakeSOClient).listModules();