From 57ed1aa71a8e80194425e10e6c5ea60618e2c4c1 Mon Sep 17 00:00:00 2001
From: maalej <maalej@sentrysoftware.com>
Date: Wed, 21 Aug 2024 10:47:12 +0200
Subject: [PATCH] Issue #94: Create WindowsProcess connector

* Add comments to explain the connector variables configuration in
  WindowsProcess.yaml
---
 .../system/WindowsProcess/WindowsProcess.yaml  | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/src/main/connector/system/WindowsProcess/WindowsProcess.yaml b/src/main/connector/system/WindowsProcess/WindowsProcess.yaml
index ba84731..8cb554d 100644
--- a/src/main/connector/system/WindowsProcess/WindowsProcess.yaml
+++ b/src/main/connector/system/WindowsProcess/WindowsProcess.yaml
@@ -100,7 +100,23 @@ monitors:
             FROM
               processQuery
             WHERE
-              Name IN ${var::processName}
+              Name IN ${var::processNames}
+
+            # The value of the variable 'processNames'
+            # is set in MetricsHub configuration file 'metricshub.yaml'. Here is an example:
+            # resources:
+            #  localhost:
+            #    attributes:
+            #      host.name: localhost:
+            #      host.type: windows
+            #    protocols:
+            #      wmi:
+            #        timeout: 120
+            #    connectors: ["+WindowsProcess"]
+            #    variables:
+            #      WindowsProcess:
+            #        processNames: ('msedge.exe', 'process2.exe')
+
       mapping:
         source: ${source::sqlQuery}
         attributes: