chore(nextcloud): fixed yml & style edit

newrelic · May 22, 2023 · f54b16a · f54b16a
1 parent 15cd3e8
commit f54b16a
Showing 1 changed file with 47 additions and 47 deletions.
diff --git a/...frastructure/host-integrations/host-integrations-list/nextcloud-integration.mdx b/...frastructure/host-integrations/host-integrations-list/nextcloud-integration.mdx
@@ -110,54 +110,54 @@ With the infrastructure agent installed, you need to establish a line of communi
 
 1. Follow our instructions to install our [Prometheus OpenMetrics integration](/docs/infrastructure/prometheus-integrations/install-configure-openmetrics/install-update-or-uninstall-your-prometheus-openmetrics-integration). 
 2. Navigate to `/etc/newrelic-infra/integrations.d`, the folder you installed the Prometheus OpenMetrics integration in, and create a file named `nri-prometheus.config.yml`.
-3. To get server-related information, replace the URL inside the targets in our [sample file](https://github.com/newrelic/nri-prometheus/blob/main/configs/nri-prometheus-config.yml.sample). The URL should match the URL associated with your exposed Nextcloud metrics:
+3. Copy the contents of the [`nri-prometheus.config.yml` sample file](https://github.com/newrelic/nri-prometheus/blob/main/configs/nri-prometheus-config.yml.sample), and paste them in your `nri-prometheus.config.yml` file. To get server-related information, replace the URL inside the targets in our. The URL should match the URL associated with your exposed Nextcloud metrics:
   ```yml
-  integrations:
-  - name: nri-prometheus
-    config:
-      # When standalone is set to false nri-prometheus requires an infrastructure agent to work and send data. Defaults to true
-      standalone: false
-
-      # When running with infrastructure agent emitters will have to include infra-sdk
-      emitters: infra-sdk
-
-      # The name of your cluster. It's important to match other New Relic products to relate the data.
-      cluster_name: "my_exporter"
-
-      targets:
-        - description: Secure etcd example
-          urls: ["http://127.0.0.1:9205"]
-      #    tls_config:
-      #      ca_file_path: "/etc/etcd/etcd-client-ca.crt"
-      #      cert_file_path: "/etc/etcd/etcd-client.crt"
-      #      key_file_path: "/etc/etcd/etcd-client.key"
-
-      # Whether the integration should run in verbose mode or not. Defaults to false.
-      verbose: false
-
-      # Whether the integration should run in audit mode or not. Defaults to false.
-      # Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
-      # It does not include verbose mode. This can lead to a high log volume, use with care.
-      audit: false
-
-      # The HTTP client timeout when fetching data from endpoints. Defaults to "5s" if it is not set.
-      # scrape_timeout: "5s"
-
-      # Length in time to distribute the scraping from the endpoints. Default to "30s" if it is not set.
-      scrape_duration: "5s"
-
-      # Number of worker threads used for scraping targets.
-      # For large clusters with many (>400) endpoints, slowly increase until scrape
-      # time falls between the desired `scrape_duration`.
-      # Increasing this value too much will result in huge memory consumption if too
-      # many metrics are being scraped.
-      # Default: 4
-      # worker_threads: 4
-
-      # Whether the integration should skip TLS verification or not. Defaults to false.
-      insecure_skip_verify: false
-
-    timeout: 10s
+    integrations:
+    - name: nri-prometheus
+      config:
+        # When standalone is set to false nri-prometheus requires an infrastructure agent to work and send data. Defaults to true
+        standalone: false
+
+        # When running with infrastructure agent emitters will have to include infra-sdk
+        emitters: infra-sdk
+
+        # The name of your cluster. It's important to match other New Relic products to relate the data.
+        cluster_name: "my_exporter"
+
+        targets:
+          - description: Secure etcd example
+            urls: ["http://127.0.0.1:9205"]
+        #    tls_config:
+        #      ca_file_path: "/etc/etcd/etcd-client-ca.crt"
+        #      cert_file_path: "/etc/etcd/etcd-client.crt"
+        #      key_file_path: "/etc/etcd/etcd-client.key"
+
+        # Whether the integration should run in verbose mode or not. Defaults to false.
+        verbose: false
+
+        # Whether the integration should run in audit mode or not. Defaults to false.
+        # Audit mode logs the uncompressed data sent to New Relic. Use this to log all data sent.
+        # It does not include verbose mode. This can lead to a high log volume, use with care.
+        audit: false
+
+        # The HTTP client timeout when fetching data from endpoints. Defaults to "5s" if it is not set.
+        # scrape_timeout: "5s"
+
+        # Length in time to distribute the scraping from the endpoints. Default to "30s" if it is not set.
+        scrape_duration: "5s"
+
+        # Number of worker threads used for scraping targets.
+        # For large clusters with many (>400) endpoints, slowly increase until scrape
+        # time falls between the desired `scrape_duration`.
+        # Increasing this value too much will result in huge memory consumption if too
+        # many metrics are being scraped.
+        # Default: 4
+        # worker_threads: 4
+
+        # Whether the integration should skip TLS verification or not. Defaults to false.
+        insecure_skip_verify: false
+
+      timeout: 10s
   ```
 
 4. [Restart your New Relic infrastructure service](/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent).