HELM configuration

local.trinityCore.maxPayloadSizeInMb

The maximum payload size in MB that trinity-core-service accepts via HTTP. The payload size is taken from the header and does not cover intentional misuse.

no

5

local.trinityCore.tokenCacheEnabled

Enables or disables the caching of MACMA tokens.

no

true

local.trinityCore.tokenCacheTimeToLive

Time a token MACMA token is cached.

no

30s

local.trinityCore.amqpPrefetch

Number of AMQP0.9.1 messages to prefetch.

no

20

local.trinityCore.amqpNumberOfConsumers

Number of AMQP consumers.

no

5

local.trinityCore.amqpNumberOfMaxConsumers

Maximum number of AMQP consumers.

no

10

local.trinityCore.processFilterAutocompletionTimeLimitationInDays

This parameter adds a time limitation to the database query for reading data, used in the auto-completion. This can be set for improving performance on environments with a high retention configuration.

no

14

local.trinityCore.missingPermissionReCheckSchedulerTimeInMin

This property sets the scheduler interval where a tenant’s MDM master data synchronization is retried after PQM got a missing permission error.

no

1

local.trinityCore.orphanDetectionCriteriaInHours

This property defines after what time a stale migration is considered orphan and picked up by the orphan detection scheduler.

no

3

local.trinityCore.orphanDetectionSchedulerTimeInMin

This property sets the scheduler interval to identify and recover orphan synchronizations. This can occur if a service instance is stopped within a synchronization. A recovery will be started ones detected.

no

30

local.trinityCore.corruptedDetectionSchedulerTimeInMin

This property sets the scheduler interval where a tenant’s MDM master data synchronization is retried after PQM detected a corrupted state.

no

1

local.trinityCore.datasourceMaximumPoolSize

Maximum pool size for datasource.

no

20

local.trinityCore.maxDbConnectionLifetime

If maxLifetime is configured, create a future End-of-life task with 2.5% variance from the maxLifetime time to ensure there is no massive die-off of Connections in the pool. Defaults to 110000 ms (110s) which is lower than the AzureSQL default (which is 120s).

no

110000

local.trinityCore.relationalDbMaxBatchSize

The maximum number records that are to a batch in one transaction before persisting in the database.

no

10

local.trinityCore.intelligenceBatchMaxSize

The maximum number of intelligence records that add added to a batch before persisting in the database. This should be aligned with 'local.trinityCore.relationalDbMaxBatchSize'.

no

10

local.influxDb.logLevel

Log level for InfluxDB

no

NONE

local.influxDb.retentionPolicyReplication

The attribute of the retention policy that determines how many copies of the data are stored in the cluster. Replicating copies ensures that data is accessible when one or more data nodes are unavailable. InfluxDB replicates data across N data nodes, where N is the replication factor. Note: This property is only considered when PQM creates the database. PQM only creates the database if the database does not exist at the service startup and if the database user has the relevant permissions. Also, this parameter will be considered only ones on database creation time. Changing this configuration at a later point in time needs to be done in the database.

no

1

local.influxDb.processRetentionPolicyDuration

The process retention policy configuration has two responsibilities:

. Setting the retention policy. Retention policy is the part of InfluxDB data structure that describes for how long InfluxDB keeps data. Note: The retention policy is only set when PQM creates the database. PQM only creates the database if the database does not exist at the service startup and if the database user has the relevant permissions. Also, this parameter will be considered only ones on database creation time. Changing this configuration at a later point in time needs to be done in the database.

. Defines how far into the past processes are searched for. Important: If the retention policy is set in the database, this configuration must also be set to this configuration property. A mismatch between the database configuration and this property negatively impact the system functionality. E.g. processes cannot be found.

no

14d

local.influxDb.overwriteProcesses

Defines if sending a process with the same timestamp again will override an existing process in the database or not.

no

true

local.influxDb.processBatchNumberActions

Number of actions when persisting process messages in the InfluxDB. Consult the InfluxDB documentation for more information.

no

200

local.influxDb.processBatchBufferLimit

Number of the batch buffer limit when persisting process messages in the InfluxDB. Consult the InfluxDB documentation for more information.

no

5000

local.logging.framework

Log level for framework

no

INFO

local.logging.amqp

Log level for AMQP

no

INFO

local.logging.messaging

Log level for messaging

no

INFO

local.logging.security

Log level for security

no

INFO

local.logging.springweb

Log level for Spring Web

no

INFO

local.logging.webserver

Log level for web server

no

INFO

local.logging.databaseMigration

Log level for database migration

no

INFO

local.logging.hibernate

Log level for Hibernate

no

WARN

local.logging.metrics

Log level for metrics

no

WARN