Log Properties

Log Properties

This section describes the log-related properties that you can set in the STR and the Desktop.

All Pico Types

These properties apply to all pico types in the STR.

Property

Description

SOC 1

Category

Reason

Property

Description

SOC 1

Category

Reason

pico.logdateformat

Default value: "YYYY-MM-DD"

This property specifies the date format to be used in the log files.

See https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/text/SimpleDateFormat.html for further information.

Yes

Integrity

Consistent timestamps enable reliable log parsing and correlation.

pico.log.header

Default value: " "

This property enables the addition of a header to the log file generated, which indicates which pico, and in which version of MediationZone the log file is generated. To add headers to the log of the pico in which you set this property, set this property to mz.version-pico

After setting this property you must restart the relevant pico.

Yes

Integrity

Adds provenance/context to logs for trustworthy evidence.

pico.log.level

Default value: "WARNING"

This property specifies the log level.

The available values for pico.log.level are:

  • ALL

  • FINEST

  • FINER

  • FINE

  • INFO

  • WARNING

  • SEVERE

  • OFF

Note!

Changing the default log level to INFO, FINE, FINER, FINEST, or ALL, may have a significant impact on performance.

Yes

Integrity

Determines logging detail; too low undermines audit evidence.

pico.pid

Default value: $MZ_HOME/log/${pico.name}.pid

This property specifies the directory and filename you want the EC or Platform to write process ID (PID) to. The value after the last forward slash ( / ) will always be the filename.

If this property is not included in the pico configuration, the default directory and filename, $MZ_HOME/log/${pico.name}.pid will be used.

Note!

If you are using your own directory and have several ECs, you will have to manually create the directory for each EC.

Yes

Availability

PID file enables supervision/restart tooling to keep services running.

pico.stderr

Default value: $MZ_HOME/log/${pico.name}.log

This property specifies the directory and filename you want the EC or Platform to write standard errors to. The value after the last forward slash ( / ) will always be the filename.

If this property is not included in the pico configuration, the default directory and filename, $MZ_HOME/log/${pico.name}.log will be used.

Note!

If you are using your own directory and have several ECs, you will have to manually create the directory for each EC.

Yes

Integrity

Captures error output needed for accurate troubleshooting/audit.

pico.stdout

Default value: $MZ_HOME/log/${pico.name}.log

This property specifies the directory and filename you want the EC or Platform to write standard output to. The value after the last forward slash ( / ) will always be the filename.

If this property is not included in the pico configuration, the default directory and filename, $MZ_HOME/log/${pico.name}.log will be used.

Note!

If you are using your own directory and have several ECs, you will have to manually create the directory for each EC.

Yes

Integrity

Captures runtime output for complete operational records.

log4j.configurationFile

Default value: $MZ_HOME/etc/log4j2.xml

This property specifies the location of log4j2 configuration file.

If this property is not included in the pico configuration, the default directory, $MZ_HOME/etc/log4j2.xml will be used.

Yes

Integrity

Controls logging configuration to ensure correct, tamper-evident logs.

log4j APL Logs - Platform

The Platform property mz.logging.refreshinterval defines how often log4j APL logs are updated. It is set to 1000 ms by default. For further information about log4j APL logs, see log4j APL Logging Configurations.