docs(i18n): sync content/ja/docs/collector/architecture.md

[aki0000]

• I have read and followed the Contributing docs, especially the "First-time contributing?" section.
• This PR has content that I did not fully write myself.
  • I used AI and I have read and followed the Generative AI Contribution Policy.
• I have the experience and knowledge necessary to understand, review, and validate all content in this PR.¹

---

English Page

https://opentelemetry.io/docs/collector/architecture/

Current ja Page

https://opentelemetry.io/ja/docs/collector/architecture/

Preview Page

https://deploy-preview-9511--opentelemetry.netlify.app/ja/docs/collector/architecture/

Could you review this PR ? Because I just saw this page at work.

Footnotes

1. Yes, I can answer maintainer questions about the content of this PR, without using AI. ↩

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-      processors: [memory_limiter, batch]
+      processors: [memory_limiter]

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-with two receivers, two processors, and two exporters.
+with two receivers, one processor, and two exporters.

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-      processors: [memory_limiter, batch]
+      processors: [memory_limiter]

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-{{% alert title="Important" color="warning" %}}
-
-When the same receiver is referenced in more than one pipeline, the Collector
-creates only one receiver instance at runtime that sends the data to a fan-out
-consumer. The fan-out consumer in turn sends the data to the first processor of
-each pipeline. The data propagation from receiver to the fan-out consumer and
-then to processors is completed using a synchronous function call. This means
-that if one processor blocks the call, the other pipelines attached to this
-receiver are blocked from receiving the same data, and the receiver itself stops
-processing and forwarding newly received data.
-
-{{% /alert %}}
+> [!WARNING]
+>
+> When the same receiver is referenced in more than one pipeline, the Collector
+> creates only one receiver instance at runtime that sends the data to a fan-out
+> consumer. The fan-out consumer in turn sends the data to the first processor
+> of each pipeline. The data propagation from receiver to the fan-out consumer
+> and then to processors is completed using a synchronous function call. This
+> means that if one processor blocks the call, the other pipelines attached to
+> this receiver are blocked from receiving the same data, and the receiver
+> itself stops processing and forwarding newly received data.

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-never shared between pipelines. For example, if `batch` processor is used in
-several pipelines, each pipeline has its own batch processor, but each batch
-processor is configured exactly the same way if they reference the same key in
-the configuration. See the following configuration:
+never shared between pipelines. For example, if the `transform` processor is
+used in several pipelines, each pipeline has its own transform processor, but
+each transform processor is configured exactly the same way if they reference
+the same key in the configuration. See the following configuration:

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

 ```yaml
 processors:
-  batch:
-    send_batch_size: 10000
-    timeout: 10s
+  transform:
+    error_mode: ignore
+    trace_statements:
+      - set(resource.attributes["namespace"],
+        resource.attributes["k8s.namespace.name"])
+      - delete_key(resource.attributes, "k8s.namespace.name")
 
 service:
   pipelines:
     traces: # a pipeline of “traces” type
       receivers: [zipkin]
-      processors: [batch]
+      processors: [transform]
       exporters: [otlp]
     traces/2: # another pipeline of “traces” type
       receivers: [otlp]
-      processors: [batch]
+      processors: [transform]
       exporters: [otlp]

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-  R1("`zipkin Receiver`") --> P1["`#quot;batch#quot; Processor`"]
+  R1("`zipkin Receiver`") --> P1["`#quot;transform#quot; Processor`"]

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-  R1("`otlp Receiver`") --> P1["`#quot;batch#quot; Processor`"]
+  R1("`otlp Receiver`") --> P1["`#quot;transform#quot; Processor`"]

[aki0000]

diff of org English markdown with 748555c22f43476291ae0c7974ca4a2577da0472

-Note that each `batch` processor is an independent instance, although they are
-configured the same way with a `send_batch_size` of `10000`.
+Note that each `transform` processor is an independent instance, although they
+are configured the same way with a `send_batch_size` of `10000`.

[kohbis]

ドリフトの修正いただいたときはこちらもあわせて削除お願い致します 🙇

Suggested change

drifted_from_default: true

[kohbis]

@aki0000 翻訳自体はLGTMでした 🙇
（差分もわかりやすくしていただきありがとうございます）

1点だけ細かいところでコメントしております