KNW-2200 pick-25 translation done, a few corrections to structure

Author: Mattias Schlenker

src/common/en/opentelemetry.asciidoc

@@ -42,25 +42,22 @@ ifdef::saas[]
 * _Logs_ and _traces_ are currently not supported by {CE}.
 endif::[]
 
-// start translation
-////
-Für die Einrichtung stehen zwei Wege bereit:
+There are two ways to set this up:
 
 ifdef::onprem[]
-* Seit {CMK} {v25}p9 ist ein xref:setup[Assistent] verfügbar, der Schritt für Schritt durch die Einrichtung führt und die Komponenten xref:metric_backend#[Metrik-Backend] sowie die xref:dcd[dynamische Host-Verwaltung] mit sinnvollen Standardeinstellungen versieht.
+* Starting with {CMK} {v25}p9, a xref:setup[wizard] is available that guides you step by step through the setup process and configures the xref:metric_backend#[metric backend] and xref:dcd[dynamic host management] components with appropriate default settings.
 endif::[]
 ifdef::saas[]
-* Seit Juli 2026 ist ein xref:setup[Assistent] verfügbar, der Schritt für Schritt durch die Einrichtung führt und alle Komponenten inklusive der xref:dcd[dynamischen Host-Verwaltung] mit sinnvollen Standardeinstellungen versieht.
+* Since July 2026, a xref:setup[wizard] is available that guides you step by step through the setup process and configures all components—including xref:dcd[dynamic host management]—with appropriate default settings.
 endif::[]
-* Alternativ können Sie die beteiligten Komponenten xref:setup_manual[manuell einrichten], was natürlich Kenntnisse des Zusammenspiels erfordert.
+* Alternatively, you can xref:setup_manual[manually configure] the relevant components, which of course requires knowledge of how these interact.
 
 ifdef::onprem[]
-Wenn Sie _lediglich_ Logs zur Event Console schicken wollen, benötigen Sie kein Metrik-Backend.
+If you _only_ want to send logs to the Event Console, you do not need a metrics backend.
 endif::[]
-Falls Sie aus den OpenTelemetry-Metriken _nicht_ automatisch Hosts generieren wollen, brauchen Sie keine dynamische Host-Verwaltung.
-Konfigurieren Sie in diesen beiden Fällen die benötigten Komponenten manuell.
-////
-// end translation
+If you do _not_ want to automatically generate hosts from the OpenTelemetry metrics, you do not need dynamic host management.
+In both of these cases, configure the required components manually.
+
 
 [TIP]
 ====
@@ -71,43 +68,40 @@ ifdef::saas[]
 This article describes the status of the OpenTelemetry integration as of July 2026.
 endif::[]
 We are continuing to work on incorporating changes made since then.
-Please refer to the link:https://checkmk.com/werks?search=otel&product=cmk&cmk_version%5B%5D=2.5&level%5B%5D=1&level%5B%5D=2&level%5B%5D=3&class%5B%5D=feature&class%5B%5D=fix&class%5B%5D=security&edition=all[OpenTelemetry-related Werks^] to find out the current status of the {CMK} version you are using.
+Please make use of the link:https://checkmk.com/werks?search=otel&product=cmk&cmk_version%5B%5D=2.5&level%5B%5D=1&level%5B%5D=2&level%5B%5D=3&class%5B%5D=feature&class%5B%5D=fix&class%5B%5D=security&edition=all[OpenTelemetry-related works^] to determine the current status of the {CMK} version you are using.
 ====
 
 
-// start translation
-////
 [#setup]
-== Geführte Einrichtung
+== Guided Setup
 
 ifdef::onprem[]
-Den Assistenten für die Einrichtung finden Sie unter [.guihint]#Setup > Open Telemetry Quick Setup#, den analog zu konfigurierenden OpenTelemetry Collector als Prometheus Scraper unter [.guihint]#Setup > Prometheus Quick Setup#.
-Im Assistenten geben Sie die Interfaces, Ports und Protokolle an, beziehungsweise konfigurieren Scraping-Endpunkte.
+You can find the setup wizard under [.guihint]#Setup > Open Telemetry Quick Setup#, and the OpenTelemetry Collector—which is configured in the same way—as a Prometheus scraper under [.guihint]#Setup > Prometheus Quick Setup#.
+In the wizard, specify the interfaces, ports, and protocols, or configure scraping endpoints.
 endif::[]
 ifdef::saas[]
-Den Assistenten für die Einrichtung finden Sie unter [.guihint]#Setup > Open Telemetry Quick Setup#.
-Im Assistenten geben Sie die Ports und Protokolle an.
+You can find the setup wizard under [.guihint]#Setup > Open Telemetry Quick Setup#.
+In the wizard, specify the ports and protocols.
 endif::[]
-Bei Einrichtung des OpenTelemetry Collectors wird Ihnen im dritten Schritt eine Musterkonfiguration für zwischengeschaltete Kollektoren angezeigt.
-Sie können diese auf Filterung oder Begrenzung der Sendeintervalle erweitern.
-Hierbei hilft Ihnen die Dokumentation zu link:https://opentelemetry.io/docs/collector/transforming-telemetry/[_Transforming telemetry_^] des OpenTelemetry-Projekts.
+When setting up the OpenTelemetry Collector, a sample configuration for intermediate collectors is displayed in the third step.
+You can extend this to include filtering or limiting the transmission intervals.
+The documentation at link:https://opentelemetry.io/docs/collector/transforming-telemetry/[_Transforming telemetry_^] of the OpenTelemetry project will help you with this.
 
-.Der Assistent fragt relevante Optionen ab und konfiguriert benötigte Komponenten automatisch mit sinnvollen Standardeinstellungen.
-image::opentelemetry_quick_setup_onprem.png[alt="Der OpenTelemetry-Einrichtungsassistent mit geöffnetem Schritt zur Konfiguration des GRPC-Receivers."]
+.The wizard prompts you for relevant options and automatically configures the necessary components with appropriate default settings.
+image::opentelemetry_quick_setup_onprem.png[alt="The OpenTelemetry setup wizard with the step for configuring the GRPC receiver open."]
 
-Wenn Sie nach abgeschlossener Ersteinrichtung [.guihint]#Setup > Open Telemetry Quick Setup#
+// Once the initial setup is complete, i
+If you select [.guihint]#Setup > Open Telemetry Quick Setup#
 ifdef::onprem[]
-oder [.guihint]#Setup > Prometheus Quick Setup#
+or [.guihint]#Setup > Prometheus Quick Setup#
 endif::[]
-aufrufen, haben Sie die Möglichkeit, Ihre vorhandene Konfiguration anzupassen.
-Statt erneut eine geführte Einrichtung zu durchlaufen, erlauben Ihnen die beiden Knöpfe [.guihint]#OpenTelemetry Collector# und [.guihint]#Dynamic host management#, zur Einrichtung der jeweiligen Komponente zu gelangen.
+after having completed the initial setup, you will have the option to customize your existing configuration.
+Instead of going through a guided setup again, the two buttons [.guihint]#OpenTelemetry Collector# and [.guihint]#Dynamic host management# allow you to proceed directly to setting up the respective component.
 
-.Nach abgeschlossenem _Quick Setup_ können Sie in die Konfiguration der Einzelkomponenten wechseln.
-image::opentelemetry_quick_setup_edit.png[alt="Quick Setup Seite, nachdem der Assistent abgeschlossen wurde: zwei Schaltflächen für 'OpenTelemetry  Collector' und 'Dynamic host management'."]
+.Once the _Quick Setup_ is complete, you can switch to configuring the individual components.
+image::opentelemetry_quick_setup_edit.png[alt="Quick Setup page after the wizard has completed: two buttons for 'OpenTelemetry Collector' and 'Dynamic host management'."]
 
-Den bei direkter Anpassung der Einzelkomponenten größeren Umfang an Konfigurationsmöglichkeiten zeigen wir Ihnen im folgenden Abschnitt zur xref:setup_manual[manuellen Einrichtung] und xref:dcd[Einrichtung der dynamischen Host-Verwaltung].
-////
-// end translation
+We will show you the wider range of configuration options available when customizing individual components directly in the following sections on xref:setup_manual[manual setup] and xref:dcd[setting up dynamic host management].
 
 
 ifdef::onprem[]
@@ -258,23 +252,15 @@ Each die roll you trigger in this way is transmitted to {CMK} as a data point.
 
 There are three main ways to make use of incoming data in monitoring.
 This chapter introduces these three options.
-The scope of the generated services and visible metrics, as well as the flexibility and system load, differ across all of the methods.
+The amount of the generated services and visible metrics, as well as the flexibility and system load, differ across all of the methods.
 For this reason, it is important to choose the appropriate monitoring method for each application scenario.
 
-* The xref:graphing#custom_graphs[custom graphs] visualize data directly from the metrics backend in dashboards — without going through services and without even involving the monitoring core.
+* The xref:graphing#custom_graphs[custom graphs] visualize data directly from the metrics backend in dashboards—without going through services and without even involving the monitoring core.
 You can create rules for the special agent described in the following list item directly from custom graphs.
 
-// delete from here
-* Using xref:special_agent_option[special agent for selected metrics] is useful when you want to assign some data points received via OpenTelemetry to existing or newly created hosts, and are looking for a way to map data from different sources to the hosts to which they belong organizationally or technically.
-The overhead of this method is slightly higher, which is usually offset by the fact that a smaller volume of data is queried.
-// delete to here
-// start translation
-////
-* Die Verwendung von xref:special_agent_option[Custom Metrics] (über die Erstellung von _custom queries_) ist dann sinnvoll, wenn Sie einige per OpenTelemetry empfangene Datenpunkte vorhandenen oder extra angelegten Hosts zuordnen wollen.
-Dies schafft die Möglichkeit, Daten aus unterschiedlichen Quellen den Hosts zuzuordnen, zu denen sie organisatorisch oder technisch gehören.
-Der Overhead dieser Methode ist etwas höher, was meist dadurch wett gemacht wird, dass ein geringerer Umfang an Daten abgefragt wird.
-////
-// end translation
+* Using xref:special_agent_option[Custom Metrics] (by creating _custom queries_) is useful when you want to map certain data points received via OpenTelemetry to existing or newly created hosts.
+This makes it possible to map data from different sources to the hosts to which they belong, either organizationally or technically.
+The overhead of this method is slightly higher, but this is usually offset by the fact that a smaller volume of data is queried.
 
 * Using xref:dcd[dynamic host management] is ideal when it is possible to precisely map OpenTelemetry services to {CMK} hosts and OpenTelemetry metrics to {CMK} services.
 Since a dedicated fetcher is used and data therefore takes a very direct path, this approach is highly efficient.
@@ -326,7 +312,7 @@ If you create multiple rules for special agents from custom graphs, only the fir
 ====
 
 .In the rules for special agents you can edit or create new custom metrics
-image::opentelemetry_special_agent_rule.png[alt="In the rules for special agents, you can edit or create new custom metrics."]
+image::opentelemetry_special_agent_rule.png[alt="In the rules for special agents you can edit or create new custom metrics."]
 
 ifdef::onprem[]
 Since the metrics generated by the special agent follow the 'classic' path through the monitoring core and RRDs, they are not affected by the xref:metric_backend#distributed[restrictions in distributed monitoring].
@@ -425,4 +411,4 @@ The thresholds for transitioning to {WARN} and {CRIT} are the memory usage thres
 
 In addition to memory usage, the service displays graphs for incoming OpenTelemetry metrics, those forwarded to the metrics backend, and those rejected.
 This can help with debugging ("Is any data even reaching the collector?") or be useful for identifying bottlenecks ("Whoa, there's always a lot of activity here at 2 a.m.!").
-endif::[]
+endif::[]