Update new setting for Apache integration.

src/content/docs/infrastructure/host-integrations/host-integrations-list/apache-monitoring-integration.mdx

@@ -101,7 +101,7 @@ To install the Apache integration, follow the instructions for your environment:
     5. [Restart the infrastructure agent](/docs/infrastructure/new-relic-infrastructure/configuration/start-stop-restart-check-infrastructure-agent-status).
 
   </Collapser>
-  
+
     <Collapser
     id="windows-install"
     title="Windows"
@@ -193,6 +193,15 @@ The Apache integration collects both metrics(**M**) and inventory(**I**) informa
 
 {' '}
 
+<tr>
+  <td>**BINARY_PATH**</td>
+  <td>Set location of the apache binary file.</td>
+  <td>N/A</td>
+  <td style={{ 'text-align': 'center' }}>I</td>
+</tr>
+
+{' '}
+
 <tr>
   <td>**CA_BUNDLE_FILE**</td>
   <td>Alternative Certificate Authority bundle file.</td>
@@ -303,6 +312,7 @@ Our default sample config file includes examples of labels; however, as they are
     ```
 
   </Collapser>
+
   <Collapser
     id="example2"
     title="HTTP BASIC AUTHENTICATION"
@@ -337,6 +347,39 @@ Our default sample config file includes examples of labels; however, as they are
 
   <Collapser
     id="example3"
+    title="CUSTOM APACHE BINARY LOCATION"
+  >
+    By default the integration tries to detect the Apache binary on these 2 different locations: `/usr/sbin/httpd` and `/usr/sbin/apache2ctl`.<br/>If your Apache is installed on a custom location or you are using MS Windows, use the `BINARY_PATH` setting to specify the correct location and filename of your Apache binary:
+
+    ```
+    integrations:
+      - name: nri-apache
+        env:
+          METRICS: "true"
+          STATUS_URL: http://127.0.0.1/server-status?auto
+          REMOTE_MONITORING: true
+        interval: 15s
+        labels:
+          env: production
+          role: load_balancer
+
+      - name: nri-apache
+        env:
+          INVENTORY: "true"
+          STATUS_URL: http://127.0.0.1/server-status?auto
+          BINARY_PATH: 'C:\Apache\bin\httpd.exe'
+          REMOTE_MONITORING: true
+        interval: 60s
+        labels:
+          env: production
+          role: load_balancer
+        inventory_source: config/apache
+    ```
+
+  </Collapser>
+
+  <Collapser
+    id="example4"
     title="METRICS ONLY WITH SELF-SIGNED CERTIFICATE"
   >
     In this configuration we only have one integration block with `METRICS: true` to collect only metrics and added `VALIDATE_CERTS: false` to prevent validation of the server's SSL certificate when using a self-signed one:
@@ -358,7 +401,7 @@ Our default sample config file includes examples of labels; however, as they are
   </Collapser>
 
   <Collapser
-    id="example4"
+    id="example5"
     title="METRICS ONLY WITH ALTERNATIVE CERTIFICATE"
   >
     In this configuration we only have one integration block with `METRICS: true` to collect only metrics and added `CA_BUNDLE_FILE` pointing to an alternative certificate file:
@@ -380,7 +423,7 @@ Our default sample config file includes examples of labels; however, as they are
   </Collapser>
 
   <Collapser
-    id="example5"
+    id="example6"
     title="ENVIRONMENT VARIABLES REPLACEMENT"
   >
     In this configuration we are using the environment variable `APACHE_STATUS` to populate the STATUS_URL setting of the integration:
@@ -401,7 +444,7 @@ Our default sample config file includes examples of labels; however, as they are
   </Collapser>
 
   <Collapser
-    id="example6"
+    id="example7"
     title="MULTI-INSTANCE MONITORING"
   >
     In this configuration we are monitoring multiple Apache servers from the same integration. For the first instance (`STATUS_URL: https://1st_apache_host/server-status?auto`) we are collecting metrics and inventory while for the second instance (`STATUS_URL: https://2nd_apache_host/server-status?auto`) we will only collect metrics.