OBSDOCS-2521: Modularize otel-collector-target-allocator.adoc

Author: max-cx

_topic_maps/_topic_map.yml

@@ -3246,8 +3246,6 @@ Topics:
       File: otel-collector-connectors
     - Name: Extensions
       File: otel-collector-extensions
-    - Name: Target Allocator
-      File: otel-collector-target-allocator
   - Name: Configuring the instrumentation
     File: otel-configuration-of-instrumentation
   - Name: Sending traces, logs, and metrics to the Collector

modules/otel-collector-config-options.adoc

@@ -6,6 +6,7 @@
 [id="otel-collector-config-options_{context}"]
 = OpenTelemetry Collector configuration options
 
+[role="_abstract"]
 The OpenTelemetry Collector consists of five types of components that access telemetry data:
 
 * Receivers

modules/otel-collector-deployment-modes.adoc

@@ -6,6 +6,7 @@
 [id="otel-collector-deployment-modes_{context}"]
 = Deployment modes
 
+[role="_abstract"]
 The `OpenTelemetryCollector` custom resource allows you to specify one of the following deployment modes for the OpenTelemetry Collector:
 
 Deployment:: The default.

modules/otel-creating-required-RBAC-resources-automatically.adoc

@@ -6,6 +6,7 @@
 [id="otel-creating-required-RBAC-resources-automatically_{context}"]
 = Creating the required RBAC resources automatically
 
+[role="_abstract"]
 Some Collector components require configuring the RBAC resources.
 
 .Procedure

observability/otel/otel-collector/otel-collector-target-allocator.adoc renamed to modules/otel-target-allocator.adoc

@@ -1,11 +1,12 @@
-:_mod-docs-content-type: ASSEMBLY
-[id="otel-collector-target-allocator"]
-= Target Allocator
-include::_attributes/common-attributes.adoc[]
-:context: otel-collector-target-allocator
+// Module included in the following assemblies:
+//
+// * observability/otel/otel-collector/otel-collector-configuration-intro.adoc
 
-toc::[]
+:_mod-docs-content-type: REFERENCE
+[id="otel-collector-target-allocator_{context}"]
+= Target Allocator
 
+[role="_abstract"]
 The Target Allocator is an optional component of the OpenTelemetry Operator that shards scrape targets across the deployed fleet of OpenTelemetry Collector instances. The Target Allocator integrates with the Prometheus `PodMonitor` and `ServiceMonitor` custom resources (CR). When the Target Allocator is enabled, the OpenTelemetry Operator adds the `http_sd_config` field to the enabled `prometheus` receiver that connects to the Target Allocator service.
 
 :FeatureName: The Target Allocator
@@ -97,5 +98,5 @@ subjects:
     namespace: observability # <2>
 # ...
 ----
-<1> The name of the Target Allocator service account mane.
+<1> The name of the Target Allocator service account.
 <2> The namespace of the Target Allocator service account.

observability/otel/otel-collector/otel-collector-configuration-intro.adoc

@@ -1,15 +1,18 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="otel-configuration-of-otel-collector"]
-= Configuring the Collector
 include::_attributes/common-attributes.adoc[]
 :context: otel-configuration-of-otel-collector
+[id="otel-configuration-of-otel-collector_{context}"]
+= Configuring the Collector
 
 toc::[]
 
+[role="_abstract"]
 The {OTELName} Operator uses a custom resource definition (CRD) file that defines the architecture and configuration settings to be used when creating and deploying the {OTELShortName} resources. You can install the default configuration or modify the file.
 
 include::modules/otel-collector-deployment-modes.adoc[leveloffset=+1]
 
 include::modules/otel-collector-config-options.adoc[leveloffset=+1]
 
 include::modules/otel-creating-required-RBAC-resources-automatically.adoc[leveloffset=+1]
+
+include::modules/otel-target-allocator.adoc[leveloffset=+1]