Configuring Diameter Event Logger
Diameter Event Logger loads default configuration parameter values from the classpath. You can configure Diameter Event Logger listening port, output directory, and log file rollover time.
To override the default values, use a configuration source to load a custom diameter-event-logger-config.yaml file to /opt/mtx/conf. When
starting Diameter Event Logger and the custom configuration file is loaded successfully, a message is logged
to indicate which file is loaded. For
example:
[main] INFO c.m.standalone.eventlogger.Main - Reading application config file from diameter-event-logger-config.yaml
Configuration Parameters lists the Diameter Event Logger configuration parameters.
Parameter | Description | Default Value |
---|---|---|
mdc.instances | The number of DiameterEvent worker instances. Set to the number of available cores for maximum performance. | 4 |
mdc.port | The port on which the Diameter Event Logger listens for events from the Diameter Gateway. | 17030 |
json.output.directory | The directory to which the Diameter Event Logger writes the JSON log files. | /opt/mtx/data |
rollover.hour | The hour at which a new CDR file is created. | 00 |
rollover.minute | The minute at which a new CDR file is created. | 00 |
The following is an example diameter-event-logger-config.yaml
file:
mdc:
instances: 4
port: 17030
json:
output:
directory: "/opt/mtx/data/"
# interval hour (00-23)
rollover:
hour: 00
minute: 00