Merge pull request #424 from open-o11y/change_name

Modify to use the appropriate nomenclature

Author: vasireddy99

src/docs/components/ecs-metrics-receiver.mdx

@@ -202,7 +202,7 @@ where the `{ClusterName}` placeholder will be replaced with actual cluster name.
 [AWS EMF Exporter](https://aws-otel.github.io/docs/getting-started/cloudwatch-metrics) documentation to see and
 explore the metrics in Amazon CloudWatch.
 
-**Note:** AWS OpenTelemetry Collector has a [default configuration](https://github.com/aws-observability/aws-otel-collector/blob/main/config/ecs/container-insights/otel-task-metrics-config.yaml) 
+**Note:** AWS Distro for OpenTelemetry Collector has a [default configuration](https://github.com/aws-observability/aws-otel-collector/blob/main/config/ecs/container-insights/otel-task-metrics-config.yaml)
 backed into it for Container Insights experience which is smiliar to this one. Follow our [setup doc](https://aws-otel.github.io/docs/setup/ecs) to check how to use that default config.
 
 

src/docs/components/statsd-receiver.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Getting Started with StatsD Receiver in AWS OpenTelemetry Collector'
+title: 'Getting Started with StatsD Receiver in AWS Distro for OpenTelemetry Collector'
 description:
     StatsD receiver is an agent that collects [StatsD metrics](https://github.com/statsd/statsd/blob/master/docs/metric_types.md)
     and do the aggregation in a customer defined interval(default value is 60s). You can send counters, gauges and timer/histogram to StatsD receiver.

src/docs/components/x-ray-receiver.mdx

@@ -1,5 +1,5 @@
 ---
-title: 'Getting Started with X-Ray Receiver in AWS OpenTelemetry Collector'
+title: 'Getting Started with X-Ray Receiver in AWS Distro for OpenTelemetry Collector'
 description:
     AWS X-Ray is a service that collects data about requests that your application serves, and provides tools you can
     use to view, filter, and gain insights into that data to identify issues and opportunities for optimization. For

src/docs/getting-started/cloudwatch-metrics.mdx

@@ -87,9 +87,9 @@ The available dimension roll-up options in EMF exporter,
 
 ```
 awsemf:
-    log_group_name: 'AOTLogGroup'
-    log_stream_name: 'AOTLogStream'
-    namespace: 'AOTMetricNS'
+    log_group_name: 'ADOTLogGroup'
+    log_stream_name: 'ADOTLogStream'
+    namespace: 'ADOTMetricNS'
     dimension_rollup_option: 1
     log_retention: 60
 ```

src/docs/getting-started/js-sdk/metric-manual-instr.mdx

@@ -1,7 +1,7 @@
 ---
 title: 'Metrics on AWS Distro for OpenTelemetry JavaScript SDK'
 description:
-    Metrics auto instrumentation has not been supported in AOT/OpenTelemetry yet. We have to manually instrumenting code
+    Metrics auto instrumentation has not been supported in ADOT/OpenTelemetry yet. We have to manually instrumenting code
     in the application to generate application metrics. Here is an example with steps for modifying application code to
     create metrics with JavaScript SDK.
 path: '/docs/getting-started/js-sdk/metric-manual-instr'
@@ -11,7 +11,7 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 import img2 from "assets/img/docs/img2.png"
 import { Link } from "gatsby"
 
-Metrics auto instrumentation has not been supported in AOT/OpenTelemetry yet. We have to manually instrumenting code in the application to generate application metrics. Here is an example with steps for modifying application code to create metrics with JavaScript SDK.
+Metrics auto instrumentation has not been supported in ADOT/OpenTelemetry yet. We have to manually instrumenting code in the application to generate application metrics. Here is an example with steps for modifying application code to create metrics with JavaScript SDK.
 
 OpenTelemetry JavaScript SDK has provided metrics API for metrics instrumentation in applications. You can follow the steps and sample code below to create OpenTelemetry Metrics and send it over to ADOT Collector.
 

src/docs/partners/datadog.mdx

@@ -121,7 +121,7 @@ service:
       exporters: [datadog/api]
 ```
 
-Supply the relative path to this configuration file when you start the collector by passing it in using the `--config=<path/to/configuration_file>` command line argument. For examples of supplying a configuration file, see the [AWS OpenTelemetry Collector documentation](https://aws-otel.github.io/docs/getting-started/collector) for your target platform.
+Supply the relative path to this configuration file when you start the collector by passing it in using the `--config=<path/to/configuration_file>` command line argument. For examples of supplying a configuration file, see the [ADOT Collector documentation](https://aws-otel.github.io/docs/getting-started/collector) for your target platform.
 
 ## Resources
 

src/docs/partners/logzio.mdx

@@ -30,7 +30,7 @@ Once your account is created,  in the platform menu tabs, **activate** your Metr
 
 ## Configuring the Logz.io Exporter
 
-To send data to Logz.io you will need to configure the AWS OpenTelemetry collector. Trace data and Metric data are configured separately. The only change needed to your OpenTelemetry configuration is to add the Logz.io exporter. This is the component used to direct the data to Logz.io from the AWS OpenTelemetry collector.
+To send data to Logz.io you will need to configure the ADOT collector. Trace data and Metric data are configured separately. The only change needed to your OpenTelemetry configuration is to add the Logz.io exporter. This is the component used to direct the data to Logz.io from the AWS OpenTelemetry collector.
 Add a Logz.io exporter to the YAML file for your OpenTelemetry configuration, along with your Logz.io tokens.  Check out the exporter part of the [sample yaml file that is available from OpenTelemetry](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/logzioexporter). 
 
 *Note that based on your deployment, you’ll need to use your customized OpenTelemetry collector configuration changes, instead of the default OpenTelemetry file available from the AWS Distro.*

src/docs/setup/build-collector-as-debian.mdx

@@ -9,9 +9,9 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 
 <SectionSeparator />
 
-## Run AWSOTelCollector Beta on AWS EC2 Debian(ubuntu)
+## Run ADOTCollector Beta on AWS EC2 Debian(ubuntu)
 
-To run AWSOTelCollector on AWS EC2 debian host, you can choose to install AWSOTelCollector Debian on your host by the following steps.
+To run ADOTCollector on AWS EC2 debian host, you can choose to install ADOTCollector Debian on your host by the following steps.
 
 **Steps,**
 
@@ -24,23 +24,23 @@ make package-deb
 ```
 sudo dpkg -i -E ./aws-otel-collector.deb
 ```
-3. Once DEB is installed, it will create AWSOTelCollector in directory /opt/aws/aws-otel-collector/
+3. Once DEB is installed, it will create ADOTCollector in directory /opt/aws/aws-otel-collector/
 
-4. We provided a control script to manage AWSOTelCollector. Customer can use it to Start, Stop and Check Status of AWSOTelCollector.
+4. We provided a control script to manage ADOTCollector. Customer can use it to Start, Stop and Check Status of ADOTCollector.
 
-    * Start AWSOTelCollector with CTL script. The config.yaml is optional, if it is not provided the default config will be applied.
+    * Start ADOTCollector with CTL script. The config.yaml is optional, if it is not provided the default config will be applied.
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl -c </path/config.yaml> -a start
     ```
-    * Stop the running AWSOTelCollector when finish the testing.
+    * Stop the running ADOTCollector when finish the testing.
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl  -a stop
     ```
-    * Check the status of AWSOTelCollector
+    * Check the status of ADOTCollector
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl  -a status
     ```
-5. Test the data with the running AWSOTelCollector on EC2. you can run the following command on EC2 host. (Docker app has to be pre-installed)
+5. Test the data with the running ADOTCollector on EC2. you can run the following command on EC2 host. (Docker app has to be pre-installed)
 ```
 docker run --rm -it -e "otlp_endpoint=172.17.0.1:4317" -e "otlp_instance_id=test_insance" mxiamxia/aws-otel-metric-generator:latest
 ```

src/docs/setup/build-collector-as-rpm.mdx

@@ -9,9 +9,9 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 
 <SectionSeparator />
 
-## Run AWSOTelCollector Beta on AWS EC2 Linux
+## Run ADOTCollector Beta on AWS EC2 Linux
 
-To run AWSOTelCollector on AWS EC2 Linux host, you can choose to install AWSOTelCollector RPM on your host by the following steps.
+To run ADOTCollector on AWS EC2 Linux host, you can choose to install ADOTCollector RPM on your host by the following steps.
 
 **Steps,**
 
@@ -24,34 +24,34 @@ make package-rpm
 ```
 sudo rpm -Uvh  ./aws-otel-collector.rpm
 ```
-3. Once RPM is installed, it will create AWSOTelCollector in directory ```/opt/aws/aws-otel-collector/```
+3. Once RPM is installed, it will create ADOTCollector in directory ```/opt/aws/aws-otel-collector/```
 
-4. We provided a control script to manage AWSOTelCollector. Customer can use it to Start, Stop and Check Status of AWSOTelCollector.
+4. We provided a control script to manage ADOTCollector. Customer can use it to Start, Stop and Check Status of ADOTCollector.
 
-    * Start AWSOTelCollector with CTL script. The config.yaml is optional, if it is not provided the default [config](../../config.yaml) will be applied.
+    * Start ADOTCollector with CTL script. The config.yaml is optional, if it is not provided the default [config](../../config.yaml) will be applied.
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl -c </path/config.yaml> -a start
     ```
-    * Stop the running AWSOTelCollector when finish the testing.
+    * Stop the running ADOTCollector when finish the testing.
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl  -a stop
     ```
-    * Check the status of AWSOTelCollector
+    * Check the status of ADOTCollector
     ```
         sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl  -a status
     ```
 
-5. Test the data with the running AWSOTelCollector on EC2. you can run the following command on EC2 host. (Docker app has to be pre-installed)
+5. Test the data with the running ADOTCollector on EC2. you can run the following command on EC2 host. (Docker app has to be pre-installed)
 ```
-docker run --rm -it -e "OTEL_OTLP_ENDPOINT=172.17.0.1:4317" -e "otlp_instance_id=test_insance_rpm" -e "OTEL_RESOURCE_ATTRIBUTES=service.namespace=AWSOTelCollectorRPMDemo,service.name=AWSOTelCollectorRPMDemoService" -e S3_REGION=us-west-2 aottestbed/aws-otel-collector-sample-app:java-0.1.0
+docker run --rm -it -e "OTEL_OTLP_ENDPOINT=172.17.0.1:4317" -e "otlp_instance_id=test_insance_rpm" -e "OTEL_RESOURCE_ATTRIBUTES=service.namespace=ADOTCollectorRPMDemo,service.name=ADOTCollectorRPMDemoService" -e S3_REGION=us-west-2 aottestbed/aws-otel-collector-sample-app:java-0.1.0
 ```
 
 **View Your Metrics**
-You should now be able to view your metrics in your [CloudWatch console](https://console.aws.amazon.com/cloudwatch/). In the navigation bar, click on **Metrics**. The collected AWSOTelCollector metrics can be found in the **AWSOTelCollectorRPMDemo/AWSOTelCollectorRPMDemoService** namespace.
+You should now be able to view your metrics in your [CloudWatch console](https://console.aws.amazon.com/cloudwatch/). In the navigation bar, click on **Metrics**. The collected ADOTCollector metrics can be found in the **ADOTCollectorRPMDemo/ADOTCollectorRPMDemoService** namespace.
 
-### Installing AWSOTelCollector via CloudFormation
-### Install AWSOTelCollector on ECS EC2
-Download CloudFormation template file for installing AWSOTelCollector on ECS EC2 mode
+### Installing ADOTCollector via CloudFormation
+### Install ADOTCollector on ECS EC2
+Download CloudFormation template file for installing ADOTCollector on ECS EC2 mode
 ```
 curl -O https://github.com/mxiamxia/aws-opentelemetry-collector/blob/master/deployment-template/ec2/aws-otel-ec2-deployment-cfn.template
 ```
@@ -60,7 +60,7 @@ Run CloudFormation the following command once ```IAMRole```, ```Region```, ```EC
 Region=<aws-region>
 IAMRole=<iam-role>
 EC2Key=<ec2-ssh-key-name>
-aws cloudformation create-stack --stack-name AWSOTelCollectorEC2-Test \
+aws cloudformation create-stack --stack-name ADOTCollectorEC2-Test \
 	--template-body file://<CFN_File_Downloaded> \
 	--parameters ParameterKey=IAMRole,ParameterValue=${IAMRole} \
                  ParameterKey=KeyName,ParameterValue=${EC2Key} \

src/docs/setup/build-collector-on-windows.mdx

@@ -9,9 +9,9 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 
 <SectionSeparator />
 
-## Run AWSOTelCollector on AWS Windows Ec2 Host
+## Run ADOTCollector on AWS Windows Ec2 Host
 
-To run AWSOTelCollector on AWS windows ec2 host, you can choose to install AWSOTelCollector MSI on your host by the following steps.
+To run ADOTCollector on AWS windows ec2 host, you can choose to install ADOTCollector MSI on your host by the following steps.
 
 **Steps,**
 1. Login on AWS Windows EC2 host and download aws-otel-collector source code and build MSI file with the following command.
@@ -24,22 +24,22 @@ git clone https://github.com/aws-observability/aws-otel-collector.git
 msiexec /i aws-otel-collector.msi
 or can be installed by double clicking the windows msi file.
 ```
-While Installing the AWSOTelCollector it will show a popup mentioning that the software is not from verified publisher,
+While Installing the ADOTCollector it will show a popup mentioning that the software is not from verified publisher,
 this is because we have not signed the MSI one it is signed this popup will be gone
 
-3. Once MSI is installed, it will create AWSOTelCollector in directory C:\Program Files\Amazon\AwsOpentelemetryCollector
+3. Once MSI is installed, it will create ADOTCollector in directory C:\Program Files\Amazon\AwsOpentelemetryCollector
 
-4. We provided a control script to manage AWSOTelCollector. Customer can use it to Start, Stop and Check Status of AWSOTelCollector.
-    * Start AWSOTelCollector with CTL script. The config.yaml is optional, if it is not provided the default config will be applied.
+4. We provided a control script to manage ADOTCollector. Customer can use it to Start, Stop and Check Status of ADOTCollector.
+    * Start ADOTCollector with CTL script. The config.yaml is optional, if it is not provided the default config will be applied.
     ```
       & '.\Program Files\Amazon\AwsOpentelemetryCollector\aws-otel-collector-ctl.ps1' -a start
     ```
-    * Stop the running AWSOTelCollector when finish the testing.
+    * Stop the running ADOTCollector when finish the testing.
     ```
       & '.\Program Files\Amazon\AwsOpentelemetryCollector\aws-otel-collector-ctl.ps1' -a stop
 
     ```
-    * Check the status of AWSOTelCollector
+    * Check the status of ADOTCollector
     ```
       & '.\Program Files\Amazon\AwsOpentelemetryCollector\aws-otel-collector-ctl.ps1' -a status
     ```