Skip to content

Commit 66ab25a

Browse files
authored
Merge pull request #64719 from pavolloffay/otel-tls-options
TRACING-3262 | Document OTEL TLS options
2 parents b9a9cf1 + 502cb14 commit 66ab25a

File tree

1 file changed

+23
-15
lines changed

1 file changed

+23
-15
lines changed

modules/distr-tracing-otel-config-collector.adoc

Lines changed: 23 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -157,12 +157,15 @@ The OTLP receiver ingests data using the OpenTelemetry protocol (OTLP).
157157
protocols:
158158
grpc:
159159
endpoint: 0.0.0.0:4317 <1>
160+
tls: <2>
161+
ca_file: ca.pem
162+
cert_file: cert.pem
163+
key_file: key.pem
164+
client_ca_file: client.pem <3>
165+
reload_interval: 1h <4>
160166
http:
161-
endpoint: 0.0.0.0:4318 <2>
162-
tls: <3>
163-
ca_file: ca.pem
164-
cert_file: cert.pem
165-
key_file: key.pem
167+
endpoint: 0.0.0.0:4318 <5>
168+
tls: <6>
166169
167170
service:
168171
pipelines:
@@ -172,8 +175,11 @@ The OTLP receiver ingests data using the OpenTelemetry protocol (OTLP).
172175
receivers: [otlp]
173176
----
174177
<1> The OTLP gRPC endpoint. If omitted, the default `+0.0.0.0:4317+` is used.
175-
<2> The OTLP HTTP endpoint. If omitted, the default `+0.0.0.0:4318+` is used.
176-
<3> The TLS server side configuration. Defines paths to TLS certificates. If omitted, TLS is disabled.
178+
<2> The server-side TLS configuration. Defines paths to TLS certificates. If omitted, TLS is disabled.
179+
<3> The path to the TLS certificate at which the server verifies a client certificate. This sets the value of `ClientCAs` and `ClientAuth` to `RequireAndVerifyClientCert` in the `TLSConfig`. For more information, see the link:https://godoc.org/crypto/tls#Config[`Config` of the Golang TLS package].
180+
<4> Specifies the time interval at which the certificate is reloaded. If the value is not set, the certificate is never reloaded. `reload_interval` accepts a string containing valid units of time such as `ns`, `us` (or `µs`), `ms`, `s`, `m`, `h`.
181+
<5> The OTLP HTTP endpoint. The default value is `+0.0.0.0:4318+`.
182+
<6> The server-side TLS configuration. For more information, see `grpc` protocol configuration section.
177183

178184
[id="jaeger-receiver_{context}"]
179185
==== Jaeger Receiver
@@ -297,7 +303,11 @@ The OTLP gRPC exporter exports data using the OpenTelemetry protocol (OTLP).
297303
ca_file: ca.pem
298304
cert_file: cert.pem
299305
key_file: key.pem
300-
headers: <3>
306+
insecure: false <3>
307+
insecure_skip_verify: false <4>
308+
reload_interval: 1h <5>
309+
server_name_override: <name> <6>
310+
headers: <7>
301311
X-Scope-OrgID: "dev"
302312
service:
303313
pipelines:
@@ -308,7 +318,11 @@ The OTLP gRPC exporter exports data using the OpenTelemetry protocol (OTLP).
308318
----
309319
<1> The OTLP gRPC endpoint. If the `+https://+` scheme is used, then client transport security is enabled and overrides the `insecure` setting in the `tls`.
310320
<2> The client side TLS configuration. Defines paths to TLS certificates.
311-
<3> Headers are sent for every RPC performed during an established connection.
321+
<3> Disables client transport security when set to `true`. The default value is `false` by default.
322+
<4> Skips verifying the certificate when set to `true`. The default value is `false`.
323+
<5> Specifies the time interval at which the certificate is reloaded. If the value is not set, the certificate is never reloaded. `reload_interval` accepts a string containing valid units of time such as `ns`, `us` (or `µs`), `ms`, `s`, `m`, `h`.
324+
<6> Overrides the virtual host name of authority such as the authority header field in requests. You can use this for testing.
325+
<7> Headers are sent for every request performed during an established connection.
312326

313327
[id="otlp-http-exporter_{context}"]
314328
==== OTLP HTTP exporter
@@ -326,9 +340,6 @@ The OTLP HTTP exporter exports data using the OpenTelemetry protocol (OTLP).
326340
otlphttp:
327341
endpoint: http://tempo-ingester:4318 <1>
328342
tls: <2>
329-
ca_file: ca.pem
330-
cert_file: cert.pem
331-
key_file: key.pem
332343
headers: <3>
333344
X-Scope-OrgID: "dev"
334345
@@ -359,9 +370,6 @@ The Jaeger exporter exports data using the Jaeger proto format through gRPC.
359370
jaeger:
360371
endpoint: jaeger-all-in-one:14250 <1>
361372
tls: <2>
362-
ca_file: ca.pem
363-
cert_file: cert.pem
364-
key_file: key.pem
365373
service:
366374
pipelines:
367375
traces:

0 commit comments

Comments
 (0)