You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/common/de/dcd.asciidoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ ifdef::onprem[]
84
84
=== OpenTelemetry-Verbindung
85
85
86
86
{cee-only}
87
-
{CMK}{v24} bietet ab{CCE}, d. h. für {CE} und {ME}, eine experimentelle Unterstützung für die Verarbeitung von link:https://opentelemetry.io/[OpenTelemetry^]-Metriken.
87
+
{CMK}{v24} bietet in{CCE} eine experimentelle Unterstützung für die Verarbeitung von link:https://opentelemetry.io/[OpenTelemetry^]-Metriken.
88
88
Dafür sammelt in {CMK} ein OpenTelemetry-Kollektor Metrikdaten, die der Kollektor per OpenTelemetry Protocol (OTLP) erhält oder über einen Prometheus-Endpunkt abruft.
89
89
Bei der Konfiguration des Kollektors werden außerdem Regeln aufgestellt, um aus den Daten Host-Namen für {CMK} zu erzeugen.
90
90
Fertig konfiguriert legt der Kollektor los, sammelt die Daten und legt sie in der {CMK}-Instanz ab mit Dateinamen, die den Host-Namen entsprechen.
@@ -205,7 +205,7 @@ ifdef::onprem[]
205
205
[#connection_properties_opentelemetry]
206
206
=== Eigenschaften einer OpenTelemetry-Verbindung
207
207
208
-
Die Optionen bei der Erstellung einer Piggyback- und OpenTelemetry-Verbindung, die ab{CE} eingerichtet werden kann, sind nahezu identisch.
208
+
Die Optionen bei der Erstellung einer Piggyback- und OpenTelemetry-Verbindung, die in{CE} eingerichtet werden kann, sind nahezu identisch.
209
209
Daher werden die Eigenschaften einer OpenTelemetry-Verbindung im Schnelldurchlauf vorgestellt.
210
210
211
211
image::dcd_connection_ot_01.png[alt="Eigenschaften einer OpenTelemetry-Verbindung."]
Copy file name to clipboardExpand all lines: src/common/en/dcd.asciidoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ ifdef::onprem[]
81
81
=== OpenTelemetry connection
82
82
83
83
{cee-only}
84
-
{CMK}{v24} offers experimental support for processing link:https://opentelemetry.io/[OpenTelemetry^] metrics starting with {CCE}, i.e., for {CE} and {ME}.
84
+
{CMK}{v24} offers in {CCE}experimental support for processing link:https://opentelemetry.io/[OpenTelemetry^] metrics.
85
85
To do this an OpenTelemetry collector in {CMK} gathers metric data that the collector receives via the OpenTelemetry Protocol (OTLP) or retrieves via a Prometheus endpoint.
86
86
When configuring the collector, rules are also set up to generate host names for {CMK} from the data.
87
87
Once configured the collector starts gathering the data and stores it in the {CMK} site with file names that correspond to the host names.
@@ -201,7 +201,7 @@ ifdef::onprem[]
201
201
[#connection_properties_opentelemetry]
202
202
=== Properties of an OpenTelemetry connection
203
203
204
-
The options for creating a piggyback and OpenTelemetry connection, which can be set up from{CE} onwards, are almost identical.
204
+
The options for creating a piggyback and OpenTelemetry connection, which can be set up in{CE}, are almost identical.
205
205
We will therefore provide a quick overview of the properties of an OpenTelemetry connection.
206
206
207
207
image::dcd_connection_ot_01.png[alt=“Properties of an OpenTelemetry connection.”]
0 commit comments