Skip to main content
Skip table of contents

Configure IronTap server

Created:  | Updated: 


application.conf parameters and syntax

Properties are customizable to meet your environment requirements.

Module

Property

Description

Default value

Notes

irontap.zos


smf.ebcdic-codepage

The default EBCDIC encoding.

IBM1047



systems

An array of system ids and time zones.


Example of system specific timezone configuration
CODE
systems: [
{id: S0W1, time-zone: EST}
{id: S0W2, time-zone: CET}
]

irontap.zos.global

time-zone

The default time zone for all z/OS systems.

CET

clock.skew

Add the provided time skew offset to the timestamps of all created spans.

0ms

Valid entry examples: 850ms, -2s

irontap.core


worker-threads

The number of threads for parallel SMF processing.

-1

Choose the number of threads. A negative value will always result in using #cores -1 threads (at least 1).

logSmfDataOnError

An SMF parsing error will be logged including the whole SMF record.

true

config.render-regex-mask

A regular expression used to remove secrets from the configuration log.

(?i).*?(token|password|secret|passphrase|keystore|truststore|jaas).*?

Example

Configuration setting:

irontap.my.secret:forYourEyesOnly

log entry:

irontap.my.secret: *** secret removed ***

irontap.sources.tcp

port

The listener port which the z/IRIS client uses to connect to z/IRIS IronTap.

irontap.sources.kafka

topicPattern

A pattern describing the topics z/IRIS IronTap should consume.

smf


consumer

Contains the Apache Kafka Consumer configuration provided by your Apache Kafka administrator.

default consumer config

irontap.storage.metrics.influxdb2

bucket

The InfluxDB bucket to be used for z/IRIS metrics

org

The InfluxDB organization

url

The url to your InfluxDB or InfluxDB receiver

authenticateToken

A token with write permissions within the organization

Configuration can also be customized via the command-line.


Example configuration

JSON
irontap{
 storage{
  metrics{
   influxdb2{
    bucket = "16b45434a5f58182"
    org = "e9043121e23a02da"
    url = "https://influx-cluster.com:32000"
    authenticateToken = "MySecureOrgToken=="
   }
  }
 }
}

irontap.db2.telemetry

datadog.trace.id.format

Specifies if the Datadog trace ID format should be used for DB2 telemetry.

Enable to make trace ID searchable in Datadog.

false

false = 128 bit hexadecimal number

true = 64 bit decimal number

irontap.zos.connect.telemetry

measurement.prefix

The prefix used for z/OS Connect measurements.

zos.connect

irontap.zos.rmf.telemetry

measurement.prefix

The prefix used for RMF measurements.

zos.rmf

irontap.zos.mq.telemetry

measurement.prefix

The prefix used for MQ measurements.

zos.mq

irontap.correlation

mode

To enable correlation set this value to LOCAL (single node) or CLUSTER (multi node, see irontap.cluster.kafka).

NONE

LOCAL, CLUSTER or NONE

correlation-info-capacity

The maximum amount of correlation information kept in memory.

1.000.000

(warning) Changing this value will affect the memory consumption of IronTap.

correlation-capacity

The maximum amount of active correlations.

4096

(warning) Changing this value will affect the memory consumption of IronTap.

timeout

The default correlation timeout, correlation related spans will be create with random traceId and spanId when the timeout is reached.

1d

1 day

irontap.cluster.kafka

(info) irontap.correlation.mode has to be set to “CLUSTER

bootstrap.servers

A list of host/port pairs used for establishing the initial connection to the Kafka cluster.

localhost:9092

topic.name

The Kafka topic used to share correlation informations between multiple IronTap instances.

ziris-correlation-info

IronTap will try to create the topic if its missing.

The cleanup.policy must be set to delete and retention.bytes must be at least 32MB

Example configuration

The example below overrides the default EBCDIC code page with IBM01140.

application.conf dot notation
YAML
irontap.zos.smf.ebcdic-codepage: "IBM01140"
application.conf JSON notation
JSON
irontap{
 zos{
  smf{
   ebcdic-codepage: "IBM01140"
  }
 }
}
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.