chore(agent-control): rename NRDOT agent type

Author: DavSanchez

src/content/docs/infrastructure-as-code/terraform/agent-control.mdx

@@ -164,7 +164,7 @@ agentControlDeployment:
         agent-operator:
           agent_type: com.newrelic.k8s_agent_operator:0.1.0
         open-telemetry:
-          agent_type: newrelic/io.opentelemetry.collector:0.1.0
+          agent_type: newrelic/com.newrelic.opentelemetry.collector:0.1.0
         gateway:
           agent_type: newrelic/com.newrelic.pipeline_control_gateway:0.1.0
     agentsConfig:

src/content/docs/new-relic-control/agent-control/configuration.mdx

@@ -717,7 +717,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 You can rename or remove either agent based on your observability requirements.
@@ -738,7 +738,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 You can rename or remove either agent based on your observability requirements.
@@ -755,7 +755,7 @@ You can also use environment variables to define the agent settings:
 Agent Control can currently manage the following pre-defined on-host agent types:
 
 * New Relic infrastructure agent: `newrelic/com.newrelic.infrastructure`. All existing features in the [infrastructure agent](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring) are supported, including orchestrating [on-host integrations](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) and our [log forwarder integration](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) based on FluentBit.
-* New Relic distribution for OpenTelemetry: `newrelic/io.opentelemetry.collector`
+* New Relic distribution for OpenTelemetry: `newrelic/com.newrelic.opentelemetry.collector`
 
 Each agent type offers a set of optional variables that can be customized to tailor its behavior. To customize the agent local configuration:
 
@@ -842,7 +842,7 @@ Here's a list of available variables for the latest agent type versions:
       </tr>
       <tr>
           <td>
-            `io.opentelemetry.collector`
+            `com.newrelic.opentelemetry.collector`
           </td>
           <td>
             `config`
@@ -856,7 +856,7 @@ Here's a list of available variables for the latest agent type versions:
       </tr>
       <tr>
           <td>
-            `io.opentelemetry.collector`
+            `com.newrelic.opentelemetry.collector`
           </td>
           <td>
             `health_check.path`
@@ -1139,7 +1139,7 @@ agents:
   nr-infra-agent:
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   #nr-otel-collector:
-  #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+  #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
   </Collapser>
 </CollapserGroup>

src/content/docs/new-relic-control/agent-control/troubleshooting.mdx

@@ -337,7 +337,7 @@ This document covers the steps to troubleshoot common issues when installing or
       "sub_agents": {
         "nr-otel-collector": {
           "agent_id": "nr-otel-collector",
-          "agent_type": "newrelic/io.opentelemetry.collector:0.1.0",
+          "agent_type": "newrelic/com.newrelic.opentelemetry.collector:0.1.0",
           "healthy": true
         },
         "nr-infra-agent": {

src/i18n/content/es/docs/new-relic-control/agent-control/configuration.mdx

@@ -671,7 +671,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Puede cambiar el nombre o eliminar cualquiera de los agentes según sus requisitos de observabilidad. El nombre del agente debe ser un nombre de etiqueta [RFC-1035 válido](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -692,7 +692,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Puede cambiar el nombre o eliminar cualquiera de los agentes según sus requisitos de observabilidad. El nombre del agente debe ser un nombre de etiqueta [RFC-1035 válido](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -709,7 +709,7 @@ También puede emplear variables de entorno para definir la configuración del a
 Actualmente, agente Control puede gestionar los siguientes tipos de agentes predefinidos en el host:
 
 * Agente de infraestructura New Relic : `newrelic/com.newrelic.infrastructure`. Se admiten todas las características existentes en el [agente de infraestructura](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring), incluida [la integración orquestada en el host](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) y nuestro [reenviador de integración de logs](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) basado en FluentBit.
-* Distribución de New Relic para OpenTelemetry: `newrelic/io.opentelemetry.collector`
+* Distribución de New Relic para OpenTelemetry: `newrelic/com.newrelic.opentelemetry.collector`
 
 Cada tipo de agente ofrece un conjunto de variables opcionales que se pueden personalizar para adaptar su comportamiento. Para personalizar la configuración local del agente:
 
@@ -817,7 +817,7 @@ A continuación se muestra una lista de variables disponibles para las últimas
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -835,7 +835,7 @@ A continuación se muestra una lista de variables disponibles para las últimas
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -1118,7 +1118,7 @@ Los siguientes ejemplos contienen casos de uso comunes que están listos para co
       nr-infra-agent:
         agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
       #nr-otel-collector:
-      #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+      #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
     ```
   </Collapser>
-</CollapserGroup>
+</CollapserGroup>

src/i18n/content/fr/docs/new-relic-control/agent-control/configuration.mdx

@@ -671,7 +671,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Vous pouvez renommer ou supprimer l’un ou l’autre des agents en fonction de vos besoins d’observabilité. Le nom de l'agent doit être un nom d'étiquette [RFC-1035 valide](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -692,7 +692,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Vous pouvez renommer ou supprimer l’un ou l’autre des agents en fonction de vos besoins d’observabilité. Le nom de l'agent doit être un nom d'étiquette [RFC-1035 valide](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -709,7 +709,7 @@ Vous pouvez également utiliser des variables d’environnement pour définir le
 Agent Control peut actuellement gérer les types d'agents sur hôte prédéfinis suivants :
 
 * Agent d'infrastructure New Relic : `newrelic/com.newrelic.infrastructure`. Toutes les fonctionnalités existantes de l' [agentinfrastructure ](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring)sont prises en charge, y compris l'orchestration [de l'intégration sur hôte](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) et [l'intégration de notre redirecteur de log](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) basé sur FluentBit.
-* Distribution New Relic pour OpenTelemetry : `newrelic/io.opentelemetry.collector`
+* Distribution New Relic pour OpenTelemetry : `newrelic/com.newrelic.opentelemetry.collector`
 
 Chaque type d'agent offre un ensemble de variables facultatives qui peuvent être personnalisées pour adapter son comportement. Pour personnaliser la configuration locale de l’agent :
 
@@ -817,7 +817,7 @@ Voici une liste des variables disponibles pour les dernières versions de type d
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -835,7 +835,7 @@ Voici une liste des variables disponibles pour les dernières versions de type d
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -1118,7 +1118,7 @@ Les exemples suivants contiennent des cas d’utilisation courants prêts à êt
       nr-infra-agent:
         agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
       #nr-otel-collector:
-      #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+      #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
     ```
   </Collapser>
-</CollapserGroup>
+</CollapserGroup>

src/i18n/content/jp/docs/new-relic-control/agent-control/configuration.mdx

@@ -671,7 +671,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 監視要件に基づいて、いずれかのエージェントの名前を変更または削除できます。 エージェント名は[有効な RFC-1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names)ラベル名である必要があります。
@@ -692,7 +692,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 監視要件に基づいて、いずれかのエージェントの名前を変更または削除できます。 エージェント名は[有効な RFC-1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names)ラベル名である必要があります。
@@ -709,7 +709,7 @@ agents:
 Agent Control現在、次の事前定義されたオンホスト エージェント タイプを管理できます。
 
 * New Relicインフラストラクチャ エージェント: `newrelic/com.newrelic.infrastructure` 。 FluentBit[ に基づく](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring) [オンホスト インワー テグレーションやログフォダー](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/)[ インテグレーションのオーケストレーションなど、インフラストラクチャ](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) エージェント の 既存の機能がすべてサポートされています。
-* OpenTelemetry の New Relic ディストリビューション: `newrelic/io.opentelemetry.collector`
+* OpenTelemetry の New Relic ディストリビューション: `newrelic/com.newrelic.opentelemetry.collector`
 
 各エージェント タイプには、その動作に合わせてカスタマイズできるオプションの変数のセットが用意されています。エージェントのローカル設定をカスタマイズするには:
 
@@ -817,7 +817,7 @@ Agent Control現在、次の事前定義されたオンホスト エージェン
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -835,7 +835,7 @@ Agent Control現在、次の事前定義されたオンホスト エージェン
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -1118,7 +1118,7 @@ Agent Control現在、次の事前定義されたオンホスト エージェン
       nr-infra-agent:
         agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
       #nr-otel-collector:
-      #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+      #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
     ```
   </Collapser>
-</CollapserGroup>
+</CollapserGroup>

src/i18n/content/kr/docs/new-relic-control/agent-control/configuration.mdx

@@ -233,7 +233,7 @@ OpenTelemetry 및 사용자 정의 수집기 설정 사용 이 예제는 OpenTel
 
 다음 예에서는 **Newrelic Control** UI 에서 개별 에이전트를 원격으로 구성하는 방법을 보여줍니다.
 
-#### 원격 설정: 뉴렐릭 인프라 
+#### 원격 설정: 뉴렐릭 인프라
 
 이 예에서는 플릿 위험을 사용하여 Kubernetes 용 뉴렐릭 인프라 에이전트를 원격으로 구성하는 방법을 보여줍니다. `enableProcessMetrics: true` 설정하여 프로세스 메트릭 수집을 활성화합니다.
 
@@ -671,7 +671,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 옵저버빌리티 요구 사항에 따라 요원의 이름을 바꾸거나 제거할 수 있습니다. 에이전트 이름은 [유효한 RFC-1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names) 레이블 이름이어야 합니다.
@@ -692,7 +692,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 옵저버빌리티 요구 사항에 따라 요원의 이름을 바꾸거나 제거할 수 있습니다. 에이전트 이름은 [유효한 RFC-1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names) 레이블 이름이어야 합니다.
@@ -709,7 +709,7 @@ agents:
 Agent Control은 현재 다음과 같은 사전 정의된 호스트 내 에이전트 유형을 관리할 수 있습니다.
 
 * 뉴렐릭 인프라 에이전트: `newrelic/com.newrelic.infrastructure`. [온호스트 통합 오케스트레이션](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) 및 FluentBit 기반의 [리소스 전달자 통합을](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) 포함하여 전투기 [에이전트](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring) 의 모든 기존 기능이 지원됩니다.
-* OpenTelemetry 용 뉴렐릭 배포: `newrelic/io.opentelemetry.collector`
+* OpenTelemetry 용 뉴렐릭 배포: `newrelic/com.newrelic.opentelemetry.collector`
 
 각 에이전트 유형은 해당 에이전트의 동작을 맞춤화하기 위해 사용자 정의할 수 있는 선택적 변수 세트를 제공합니다. 에이전트 로컬 설정을 사용자 정의하려면:
 
@@ -817,7 +817,7 @@ Agent Control은 현재 다음과 같은 사전 정의된 호스트 내 에이
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -835,7 +835,7 @@ Agent Control은 현재 다음과 같은 사전 정의된 호스트 내 에이
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -1118,7 +1118,7 @@ Agent Control은 현재 다음과 같은 사전 정의된 호스트 내 에이
       nr-infra-agent:
         agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
       #nr-otel-collector:
-      #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+      #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
     ```
   </Collapser>
-</CollapserGroup>
+</CollapserGroup>

src/i18n/content/pt/docs/new-relic-control/agent-control/configuration.mdx

@@ -671,7 +671,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Você pode renomear ou remover qualquer agente com base em seus requisitos de observabilidade. O nome do agente deve ser um nome de rótulo [RFC-1035 válido](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -692,7 +692,7 @@ agents:
     # The supported agent type and agent type version
     agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
   nr-otel-collector:
-    agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+    agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
 ```
 
 Você pode renomear ou remover qualquer agente com base em seus requisitos de observabilidade. O nome do agente deve ser um nome de rótulo [RFC-1035 válido](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
@@ -709,7 +709,7 @@ Você também pode usar variáveis de ambiente para definir as configurações d
 O agente Control pode atualmente gerenciar os seguintes tipos de agentes predefinidos no host:
 
 * Agente New Relic Infrastructure: `newrelic/com.newrelic.infrastructure`. Todos os recursos existentes no [agente de infraestrutura](/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring) são suportados, incluindo orquestração de [integração no host](/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/) e nosso [encaminhador de integração de logs](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/) baseado em FluentBit.
-* Distribuição New Relic para OpenTelemetry: `newrelic/io.opentelemetry.collector`
+* Distribuição New Relic para OpenTelemetry: `newrelic/com.newrelic.opentelemetry.collector`
 
 Cada tipo de agente oferece um conjunto de variáveis opcionais que podem ser personalizadas para adaptar seu comportamento. Para personalizar a configuração local do agente:
 
@@ -817,7 +817,7 @@ Aqui está uma lista de variáveis disponíveis para as versões mais recentes d
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -835,7 +835,7 @@ Aqui está uma lista de variáveis disponíveis para as versões mais recentes d
 
     <tr>
       <td>
-        `io.opentelemetry.collector`
+        `com.newrelic.opentelemetry.collector`
       </td>
 
       <td>
@@ -1118,7 +1118,7 @@ Os exemplos a seguir contêm casos de uso comuns que estão prontos para copiar
       nr-infra-agent:
         agent_type: "newrelic/com.newrelic.infrastructure:0.1.0"
       #nr-otel-collector:
-      #  agent_type: "newrelic/io.opentelemetry.collector:0.1.0"
+      #  agent_type: "newrelic/com.newrelic.opentelemetry.collector:0.1.0"
     ```
   </Collapser>
-</CollapserGroup>
+</CollapserGroup>