Configuring IronTap OpenTelemetry integration
Created: | Updated:
Supported exporters
OTLP via gRPC
OTLP via gRPC
You must provide an OTLP endpoint via the irontap.apm.otel.exporter.otlp.endpoint property.
Example
-Dirontap.apm.otel.exporter.otlp.endpoint=http://localhost:4317Enable TLS
To establish an encrypted connection with an OTLP endpoint, it is necessary to employ one or more trusted certificates to verify the server's TLS credentials.
The OTLP endpoint should also be configured to enable TLS.
The property irontap.apm.otel.exporter.otlp.certificate is utilized to indicate the file path that contains the trusted certificates to be used. The file should contain one or more X.509 certificates in PEM format.
If no certificate is provided and a secure (HTTPS) endpoint is specified the host platform’s trusted root certificates are used.
Example
-Dirontap.apm.otel.exporter.otlp.certificate="path/to/certificate"Enable mTLS (mutual TLS)
In addition to TLS, it is necessary to also provide one or more trusted client certificates which will be sent to an OTLP endpoint to verify the client’s TLS credentials and to enable mTLS.
The OTLP endpoint should also be configured to enable mTLS.
The properties irontap.apm.otel.exporter.otlp.client.certificate and irontap.apm.otel.exporter.otlp.client.key are utilized to indicate the file paths that contain the client certificates and client key to use. The client certificates file should contain one or more X.509 certificates in PEM format. The client key should contain the corresponding private key in PKCS8 PEM format.
Example
-Dirontap.apm.otel.exporter.otlp.client.certificate="path/to/clientCertificate"
-Dirontap.apm.otel.exporter.otlp.client.key="path/to/clientKey"