fix(self-managed): use full config path for zeebe broker exporter

docs/components/zeebe/technical-concepts/batch-operations.md

@@ -381,9 +381,12 @@ For very large batches (100,000+ items), enabling this option causes a temporary
 
 ```yaml
 # In your broker configuration file (for example, broker.yaml)
-exporters:
-  camundaexporter:
-    args:
-      batchOperation:
-        exportItemsOnCreation: false
+zeebe:
+  broker:
+    ...
+    exporters:
+      camundaexporter:
+        args:
+          batchOperation:
+            exportItemsOnCreation: false
 ```

docs/self-managed/components/orchestration-cluster/zeebe/configuration/broker.md

@@ -920,9 +920,12 @@ Each exporter should be configured following this template:
 #### YAML snippet
 
 ```yaml
-exporters:
-  jarPath:
-  className:
+zeebe:
+  broker:
+    ...
+    exporters:
+      jarPath:
+      className:
 ```
 
 ### zeebe.broker.exporters.elasticsearch

versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md

@@ -911,9 +911,12 @@ Each exporter should be configured following this template:
 #### YAML snippet
 
 ```yaml
-exporters:
-  jarPath:
-  className:
+zeebe:
+  broker:
+    ...
+    exporters:
+      jarPath:
+      className:
 ```
 
 ### zeebe.broker.exporters.elasticsearch

versioned_docs/version-8.6/self-managed/zeebe-deployment/exporters/elasticsearch-exporter.md

@@ -43,11 +43,14 @@ The exporter can be enabled by configuring it with the `classpath` in the broker
 For example:
 
 ```yaml
-exporters:
-  elasticsearch:
-    className: io.camunda.zeebe.exporter.ElasticsearchExporter
-    args:
-    # Refer to the table below for the available args options
+zeebe:
+  broker:
+    ...
+    exporters:
+      elasticsearch:
+        className: io.camunda.zeebe.exporter.ElasticsearchExporter
+        args:
+        # Refer to the table below for the available args options
 ```
 
 The exporter can be configured by providing `args`. The table below explains all the different
@@ -172,75 +175,78 @@ Here is an example configuration of the exporter:
 
 ```yaml
 ---
-exporters:
-  elasticsearch:
-    # Elasticsearch Exporter ----------
-    # An example configuration for the elasticsearch exporter:
-    #
-    # These setting can also be overridden using the environment variables "ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_..."
-    #
-
-    className: io.camunda.zeebe.exporter.ElasticsearchExporter
-
-    args:
-      # A comma separated list of URLs pointing to the Elasticsearch instances you wish to export to.
-      # For example, if you want to connect to multiple nodes for redundancy:
-      # url: http://localhost:9200,http://localhost:9201
-      url: http://localhost:9200
-
-      bulk:
-        delay: 5
-        size: 1000
-        memoryLimit: 10485760
-
-      retention:
-        enabled: true
-        minimumAge: 30d
-        policyName: zeebe-records-retention-policy
-
-      authentication:
-        username: elastic
-        password: changeme
-
-      index:
-        prefix: zeebe-record
-        createTemplate: true
-
-        indexSuffixDatePattern: "yyyy-MM-dd"
-
-        command: false
-        event: true
-        rejection: false
-
-        commandDistribution: true
-        decisionRequirements: true
-        decision: true
-        decisionEvaluation: true
-        deployment: true
-        deploymentDistribution: true
-        error: true
-        escalation: true
-        form: true
-        incident: true
-        job: true
-        jobBatch: false
-        message: true
-        messageStartSubscription: true
-        messageSubscription: true
-        process: true
-        processEvent: false
-        processInstance: true
-        processInstanceCreation: true
-        processInstanceMigration: true
-        processInstanceModification: true
-        processMessageSubscription: true
-        resourceDeletion: true
-        signal: true
-        signalSubscription: true
-        timer: true
-        userTask: true
-        variable: true
-        variableDocument: true
+zeebe:
+  broker:
+    ...
+    exporters:
+      elasticsearch:
+        # Elasticsearch Exporter ----------
+        # An example configuration for the elasticsearch exporter:
+        #
+        # These setting can also be overridden using the environment variables "ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_..."
+        #
+
+        className: io.camunda.zeebe.exporter.ElasticsearchExporter
+
+        args:
+          # A comma separated list of URLs pointing to the Elasticsearch instances you wish to export to.
+          # For example, if you want to connect to multiple nodes for redundancy:
+          # url: http://localhost:9200,http://localhost:9201
+          url: http://localhost:9200
+
+          bulk:
+            delay: 5
+            size: 1000
+            memoryLimit: 10485760
+
+          retention:
+            enabled: true
+            minimumAge: 30d
+            policyName: zeebe-records-retention-policy
+
+          authentication:
+            username: elastic
+            password: changeme
+
+          index:
+            prefix: zeebe-record
+            createTemplate: true
+
+            indexSuffixDatePattern: "yyyy-MM-dd"
+
+            command: false
+            event: true
+            rejection: false
+
+            commandDistribution: true
+            decisionRequirements: true
+            decision: true
+            decisionEvaluation: true
+            deployment: true
+            deploymentDistribution: true
+            error: true
+            escalation: true
+            form: true
+            incident: true
+            job: true
+            jobBatch: false
+            message: true
+            messageStartSubscription: true
+            messageSubscription: true
+            process: true
+            processEvent: false
+            processInstance: true
+            processInstanceCreation: true
+            processInstanceMigration: true
+            processInstanceModification: true
+            processMessageSubscription: true
+            resourceDeletion: true
+            signal: true
+            signalSubscription: true
+            timer: true
+            userTask: true
+            variable: true
+            variableDocument: true
 ```
 
 ## Self-signed certificates
@@ -253,7 +259,6 @@ signed using trusted root certificate authorities.
 
 1.  First, create a new custom trust store which contains the same data as the default one, using PKCS12 format. To do so, find the
     location of the default `cacerts` trust store:
-
     - On Linux systems, find it at `$JAVA_HOME/lib/security/cacerts`.
     - For macOS, find it under `$(/usr/libexec/java_home)/jre/lib/security/cacerts`.
 
@@ -285,7 +290,6 @@ signed using trusted root certificate authorities.
     ```
 
     Then, specify the following properties when running the application:
-
     - `javax.net.ssl.trustStore`: must be set to the path of your custom trust store.
     - `javax.net.ssl.trustStorePassword`: set to your trust store password.