Configure IronTap container
Created , Updated
Properties can be provided via JVM properties or a mounted configuration file.
JVM Properties
You may provide the necessary configuration via system properties. Simply set the required properties with the -D flag after the image name. Any value that exists in the configuration file can be set this way.
An OTLP endpoint needs to be set for OpenTelemetry integration
Use the following docker command to start IronTap with OpenTelemetry integration:
docker run \
--name irontap \
registry.gitlab.com/ziris/irontap:latest-kafka-otel \
-Dirontap.apm.otel.exporter.otlp.endpoint="http://collector:4317" A Datadog agent endpoint needs to be set for Datadog integration
Use the following docker command to start IronTap with Datadog integration including event propagation and required prefixes for metrics:
docker run
--name irontap \
registry.gitlab.com/ziris/irontap:latest-kafka-datadog \
-Dirontap.apm.datadog.agent.url="http://agent:8126/v0.3/traces" \
-Dirontap.apm.datadog.events.site="https://api.datadoghq.com/api/v1/events" \
-Dirontap.apm.datadog.events.apiKey="908fb9eaa85bfb05189925e0b337ac50" \
-Dirontap.zos.connect.telemetry.measurement.prefix="mainstorconcept.zos.connect" \
-Dirontap.zos.rmf.telemetry.measurement.prefix="mainstorconcept.zos.rmf" \
-Dirontap.zos.mq.telemetry.measurement.prefix="mainstorconcept.zos.mq"For more information on how to integrate IronTap containers with APMs, refer to the following documentation:
Mounted config file
A configuration file can be mounted instead of using system properties to provide the necessary configuration for the IronTap container.
An OTLP endpoint needs to be set for OpenTelemetry integration.
Use the following docker command to start IronTap with OpenTelemetry integration:
docker run \
--name irontap \
--mount type=bind,source=/host/path/to/application.conf,target=/opt/mainstorconcept/irontap/application.conf,readonly \
registry.gitlab.com/ziris/irontap:latest-kafka-otel >> Configuring IronTap container logging