Configuring IronTap Datadog integration
Created: | Updated:
Besides the general z/IRIS IronTap server configuration, some additional properties can be customized for the Datadog module. If a value is not specified, then its default value will be applied.
Metrics integration
Property | Description | Default Value |
irontap.zos.connect.telemetry | ||
---|---|---|
measurement.prefix | Datadog requires a specific prefix for z/OS Connect metrics. Need to be set to |
|
irontap.zos.rmf.telemetry | ||
measurement.prefix | Datadog requires a specific prefix for RMF metrics. Need to be set to |
|
irontap.zos.mq.telemetry | ||
measurement.prefix | Datadog requires a specific prefix for MQ metrics. Need to be set to |
|
Datadog API integration
Property | Description | Default Value |
irontap.apm.datadog.agent | ||
---|---|---|
url | Agent endpoint to submit traces |
|
irontap.apm.datadog.events | ||
site | Datadog’s site endpoint to post events to the stream. |
|
apiKey | Configured API key in Datadog |
|
irontap.apm.datadog.default.tags | ||
host | Default tag values for scoping and correlation. z/IRIS might override these default values for certain SMF types. |
|
device | ||
source | ||
env | ||
version |
Datadog Otel integration
>> IronTap integration with OpenTelemetry can be found here
irontap {
zos {
connect {
telemetry {
measurement {
prefix="mainstorconcept.zos.connect"
}
}
}
rmf {
telemetry {
measurement {
prefix="mainstorconcept.zos.rmf"
}
}
}
mq {
telemetry {
measurement {
prefix="mainstorconcept.zos.mq"
}
}
}
}
apm {
datadog {
agent {
url="http://localhost:8126/v0.3/traces"
}
events {
site="https://api.datadoghq.com/api/v1/events"
apiKey="908fb9eaa85bfb05189925e0b337ac50"
}
default {
tags {
host="S0W1"
env="prod"
version="1.9"
}
}
}
}
}