Change occurrences of Connector to Collector (#527)

signalfx · Sep 2, 2022 · 12a6734 · 12a6734
1 parent 38d05d5
commit 12a6734
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/.github/workflows/functional_test.yaml b/.github/workflows/functional_test.yaml
@@ -77,10 +77,10 @@ jobs:
           # Restart Splunk
           curl -k -u $CI_SPLUNK_USERNAME:$CI_SPLUNK_PASSWORD https://$CI_SPLUNK_HOST:$CI_SPLUNK_PORT/services/server/control/restart -X POST
 
-      - name: Deploy sck otel connector
+      - name: Deploy sck otel collector
         run: |
           export CI_SPLUNK_HOST=$(kubectl get pod splunk --template={{.status.podIP}})
-          ci_scripts/deploy_connector.sh
+          ci_scripts/deploy_collector.sh
 
       - name: Deploy log generator
         run: |

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -568,7 +568,7 @@ guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UP
 - Logs are sent through the OpenTelemetry Agent on the local node by default. `otelAgent.enabled` value must be set to `true` when using logs (#127)
 - `otelAgent.ports` and `otelCollector.ports` are selectively enabled depending on what telemetry types are enabled with `metricsEnabled`, `tracesEnabled`, and `logsEnabled`
 - Removed setting `host.name` through the `resource` processor as it is already set by the `resourcedetection/system` processor
-- Upgraded to Splunk OpenTelemetry Connector 0.26.0
+- Upgraded to Splunk OpenTelemetry Collector 0.26.0
 - Kubernetes cluster metrics now have a dimension `receiver:k8scluster` to ensure that
   MTS do not conflict with Kubernetes metrics sent by Smart Agent for the same cluster. (#134)
 

diff --git a/ci_scripts/deploy_connector.sh → ci_scripts/deploy_collector.sh b/ci_scripts/deploy_connector.sh → ci_scripts/deploy_collector.sh
diff --git a/docs/advanced-configuration.md b/docs/advanced-configuration.md
@@ -40,7 +40,7 @@ This value can be omitted if none of the values apply.
 ## Kubernetes distribution
 
 Use the `distribution` parameter to provide information about underlying
-Kubernetes deployment. This parameter allows the connector to automatically
+Kubernetes deployment. This parameter allows the collector to automatically
 scrape additional metadata. The supported options are:
 
 - `aks` - Azure AKS

diff --git a/test/README.md b/test/README.md
@@ -45,11 +45,11 @@
     kubectl port-forward pods/splunk 8000
     You can then vistit Splunk web page: https://localhost:8000
 
-#### Deploy sck otel connector
+#### Deploy sck otel collector
     # Get Splunk Host IP
     export SPLUNK_HOST=$(kubectl get pod splunk --template={{.status.podIP}})
 
-    # Use ci_scripts/sck_otel_values.yaml file to deploy sck otel connector
+    # Use ci_scripts/sck_otel_values.yaml file to deploy sck otel collector
     # Default image repository: quay.io/signalfx/splunk-otel-collector
     helm install ci-sck --set splunkPlatform.index=$CI_INDEX_EVENTS \
     --set splunkPlatform.token=$CI_SPLUNK_HEC_TOKEN \