MMM Configuration

The number of the port where the Metadata Server is running.

Default value: 8021.

The URL of the server where Keycloak is running.

Default value: http://localhost:8080/auth.

The name of the Keycloak realm.

Default value: ataccamaone.

The type of client token authentication. Valid values: BASIC, SIGNED_JWT, SECRET_JWT.

Default value: BASIC.

The client identifier used to verify the admin user’s authorization token.

Default value: mmm-admin-client.

The secret key of the client identifier for the admin account. Secret keys can be generated using Keycloak. Used by BASIC and SECRET_JWT strategies.

Default value: mmm-admin-client-s3cret.

The password of the keystore used for SIGNED_JWT authentication.

The type of the keystore used for SIGNED_JWT authentication. Possible values: JKS, PKCS12.

Default value: JKS.

The password of the keystore. Used for SIGNED_JWT authentication if the keystore is encrypted.

The private key name specified in the keystore used for SIGNED_JWT authentication.

The default value is the client identifier.

The password for the private key. Used if the private key is encrypted.

The default value is the keystore password.

Specifies for how long the JWT token used for authentication in Keycloak remains valid. Used for SIGNED_JWT and SECRET_JWT authentication strategies.

Default value: 15s. For a full list of accepted units, see Duration units.

The type of client token authentication. Valid values: BASIC, SIGNED_JWT, SECRET_JWT.

Default value: BASIC.

The client identifier. Used to verify a user’s authorization token and to log in a user.

Default value: mmm-token-client.

The secret key of the client. Secret keys can be generated using Keycloak. Used by BASIC and SECRET_JWT strategies.

Default value: mmm-token-client-s3cret.

Points to the keystore used for SIGNED_JWT authentication.

The type of the keystore used for SIGNED_JWT authentication. Possible values: JKS, PKCS12.

Default value: JKS.

The password of the keystore. Used for SIGNED_JWT authentication if the keystore is encrypted.

The private key name specified in the keystore used for SIGNED_JWT authentication.

The default value is the client identifier.

The password for the private key. Used if the private key is encrypted.

The default value is the keystore password.

Specifies for how long the JWT token used for authentication in Keycloak remains valid. Used for SIGNED_JWT and SECRET_JWT authentication strategies.

Default value: 15s. For a full list of accepted units, see Duration units.

Specifies the issuer of the JWT token. Typically, Keycloak uses the URL of the realm as the token issuer.

Default value: ${ataccama.authentication.keycloak.server-url}/realms/${ataccama.authentication.keycloak.realm}.

The expected recipients of the JWT token. Used for validating the token.

Defines for how long public keys retrieved from Keycloak are cached.

Default value: 5m. For a full list of accepted units, see Duration units.

Defines the minimum time interval between two requests for retrieving new public keys from Keycloak. This helps prevent Denial-of-Service (DoS) attacks.

Default value: 10s. For a full list of accepted units, see Duration units.

If set to true, the application uses permissions defined for the MMM module. If set to false, there are no restrictions.

If set to true, the results of the schema field obtained by querying the introspection endpoint in the GraphQL API are cached. The schema field contains the resources used in the API schema.

Defines how often a compare session should be marked as still in use. A compare session is created when a user chooses to compare two nodes and can be accessed in subsequent requests but not indefinitely.

The time interval specified here should be significantly lower than the expiration period.

Default value: 1m. For a full list of accepted units, see Duration units.

Defines the time period after which a compare session is considered expired starting from the last time the session was in use.

Expired sessions are pruned according to the pruning schedule.

Default value: 12h. For a full list of accepted units, see Duration units.

Defines the time period after which a compare session is pruned from the database starting from the last time the session was in use.

The time interval specified here must be greater than the expiration period.

Default value: 24h. For a full list of accepted units, see Duration units.

Defines how often the server attempts pruning compare sessions from the database.

Default value: 15m. For a full list of accepted units, see Duration units.

Defines how often the server attempts to detect new migration requests.

Default value: 10s. For a full list of accepted units, see Duration units.

Defines for how long a node remains read-only if a new MMD model is published. After this period expires, the migration of database schemas starts, which makes the application temporarily unavailable.

The time interval specified here needs to be long enough so that all running database transactions can be successfully completed.

Default value: 120s. For a full list of accepted units, see Duration units.

Determines whether migration is performed using the new upgrade runner (true) or the previous migration method (false).

Default value: true.

Exposes the HTTP endpoint for exporting MMM data.

The user must have the MMM_export role assigned. If set to false, exporting is not enabled.

Default value: false.

A JDBC connection string pointing to the MMM database.

Default value: jdbc:postgresql://localhost:5432/mmm?currentSchema=public.

The username for the MMM database.

Default value: one.

The password for the MMM database.

Default value: one.

Encrypted version of the same value: crypted:AES:vTlfhBo/yc94VNQ/tqAHtIzMTnEenM7WW0GAXGle4xQ=.

The maximum number of connections, both active and idle, that can be kept in the connection pool.

Default value: 30.

Defines for how long a connection can remain unoccupied outside of the connection pool before a possible connection leak is logged. Expressed in milliseconds.

Default value: 600000.

Enables the high availability setup in MMM.

Default value: false.

A JDBC connection string pointing to the high availability database.

Default value: jdbc:postgresql://localhost:5431/mmm_ha?currentSchema=public.

The username for the high availability database.

Default value: one.

The password for the high availability database.

Default value: one.

The initial sleep period before a new leader election begins. If the value is set differently on each instance, this can be used to prioritize which instance becomes active provided that there are no issues preventing that.

Default value: 0s. For a full list of accepted units, see Duration units.

Specifies how often a new active leader is elected. This affects how quickly a failed instance can be recognized and handled.

The time until a new leader is elected must be shorter or equal than the sum of this interval (distributed-leader.election-interval) and the heartbeat timeout configured for failed instances (ataccama.distributed-lock.heartbeat.timeout.dead).

Default value: 30s. For a full list of accepted units, see Duration units.

The IP address or the hostname of the server where DPM is running.

Default value: localhost.

The port where DPM is running.

Default value: 8531.

The initial interval between reconnection attempts, expressed in milliseconds.

The total time between retries is calculated as the product of the initial interval in milliseconds and the interval multiplier exponentiated by the number of the retry attempt (initialIntervalMs * intervalMultiplier ^ attemptNumber).

Default value: 500.

The multiplier of the initial time interval between reconnection attempts.

The total time between retries is calculated as the product of the initial interval in milliseconds and the interval multiplier exponentiated by the number of the retry attempt (initialIntervalMs * intervalMultiplier ^ attemptNumber).

Default value: 1.5.

The time interval after which the connection is considered stable and the retry policy is reset. A connection is considered stable if there are no errors communicating with DPM during this period. Expressed in milliseconds.

Default value: 5000.

The maximum number of threads that can be used for processing events coming from DPM.

Default value: 5.

The minimum number of threads that need to be kept alive at all times. These threads are dedicated only to processing events coming from DPM.

Default value: 2.

Defines the amount of time after which the token generated by the internal JWT generator expires. If the token expires too fast, this can lead to the following error: “UNAUTHENTICATED: Expired JWT”.

Keep in mind that extending the validity of the JWT token can potentially lead to security issues as the subscription can remain active even after the token has been revoked.

Default value: 15s. For a full list of accepted units, see Duration units.

Defines the amount of time after which the streaming token generated by the internal JWT generator expires. If the token expires too fast, this can lead to the following error: “UNAUTHENTICATED: Expired JWT”.

Keep in mind that extending the validity of the JWT token can potentially lead to security issues as the subscription can remain active even after the token has been revoked.

Default value: 4h. For a full list of accepted units, see Duration units.

The maximum number of threads that can be used for job canceling requests in case the dedicated queue is full.

Default value: 4.

The minimum number of threads that need to be kept alive at all times unless the timeout is configured. These threads are used only for job canceling requests.

Default value: 2.

The number of requests that the queue for job canceling requests can contain. Once the limit is reached, the number of threads in the pool increases to the maximum thread count.

Default value: 10.

Enables timeout for core threads in the pool for job canceling requests. In this case, the pool prioritizes starting core threads over adding requests to the pool queue.

Default value: true.

Determines whether running jobs that were started in a previous session should be recovered or canceled on the application start. In other words, the property adds a possibility to disable disaster recovery for jobs.

The following options are available:

Default value: CANCEL.

If set to true, monitoring project results are removed automatically after the set retention period expires.

For more information about custom retention configuration, which is managed through the web application, see Monitoring Project Results, Reports, and Notifications.

Default: true.

Sets how often the the application should check for results older than the defined retention period.

Default value: 1h. For a full list of accepted units, see Duration units.

Decides the maximum number of DPEs that are utilized by a single monitoring project DQ job.

Default value: 1.

Decides if rule suggestions are enabled in monitoring projects.

Default value: true.

Enables using external lineage for relationship graphs.

A JDBC connection string pointing to the external lineage database.

Default value: jdbc:postgresql://localhost:5432/mmm?currentSchema=public.

The JDBC driver class name for the external lineage database. The driver must be on the application classpath.

Default value: org.postgresql.Driver.

The username for the external lineage database.

Default value: one.

The password for the external lineage database.

Default value: one.

The name of the table containing external catalog items.

Default value: external_lineage.catalog_item.

The name of the table containing external attributes.

Default value: external_lineage.attribute.

The name of the table containing external edges.

Default value: external_lineage.edge.

The URL of the RDM GraphQL endpoint that is used for deploying configuration to RDM.

Default value: http://localhost:8060/graphql.

The total number of values for count statistics that should be stored. Applies separately to each of the following categories: frequency analysis performed on attribute level, and the related frequency groups, masks, and patterns.

Default value: 40.

The maximum allowed value is 1000, but the default one should not be increased by much to avoid performance issues.

The number of catalog items for which metadata is retrieved in a single batch for preprocessing purposes.

Before profiling starts, catalog item metadata needs to be imported, which is done in batches. A higher value improves profiling performance but can lead to issues with insufficient memory.

Default value: 50.

Defines how long the drillthrough cache stores data. Expressed in minutes.

Default value: 60.

Configures the size of the drillthrough in-memory cache. Expressed in megabytes.

Default value: 50.

Defines for how long drillthrough data is stored. By default, it is never removed.

Default value: forever (an internal constant). For a full list of accepted units, see Duration units.

Configures how often drillthroughs are removed. Should be configured with regard to drillthrough.retention-period.

Default value: 1d. For a full list of accepted units, see Duration units.

The name of the bucket in the Object Storage where drillthroughs are stored.

Default value: drillthrough.

Enables records encryption of invalid samples in shared file system.

Default value: true.

A relative path to the folder containing files that should be uploaded to the object storage.

A URL pointing to the ZIP file that should be used for data import.

Defines how the application behaves in case of an issue with data import.

Available options are as follows:

Default value: FAIL.

Configures how often to cancel lookup upload jobs that have exceeded the timeout defined in the upload-job.timeout property.

Default value: 10m. For a full list of accepted units, see Duration units.

The expiration timeout for lookup upload jobs. Jobs older that this are canceled based on the frequency defined in the upload-job.cleanup-interval property.

Default value: 60m. For a full list of accepted units, see Duration units.

Points to the folder containing the basic data that should be loaded into the application on startup.

Default value: data/basic.

Points to the folder containing the demo data that should be loaded into the application on startup.

Default value: data/demo.

The maximum number of notifications per GraphQL subscription that are cached on the backend before they are sent to the frontend.

Default value: 100.

Controls whether the SQL catalog items feature is available in the application. Enforces capability 'dsl-query-catalog-items' on generic API level.

Default value: true.

Enables the thread monitor. If set to false, the other properties configuring the thread monitor have no effect.

Default value: true.

Sets how often long running threads are sampled. The relevant statistics are periodically printed.

Default value: 30s. For a full list of accepted units, see Duration units.

Exposes the thread monitor metrics.

Default: true.

A comma-separated list of regular expressions that are applied to stack trace elements. Only the matched elements are printed to the stack trace log.

Default value: .*\\.ataccama\\..*.

A comma-separated list of regular expressions that are applied to stack trace elements. The matched elements are not printed to the stack trace log.

Default value: com\\.ataccama\\.lib\\.threadutil.*.

Enables long running thread detection for the (default) pool. Default settings can be overridden for a specific pool.

Default value: true.

Defines the threshold for long running threads. All threads running longer than the limit are considered as long running and reported. Default settings can be overridden for a specific pool.

Default value: 30s. For a full list of accepted units, see Duration units.

Enables logging all details for the thread pool, including the stack trace of long running threads. Default settings can be overridden for a specific pool.

Default value: true.

If set to true, GraphQL experimental validation is enabled. This replaces a part of the standard GraphQL query validation with an experimental one in order to improve performance.

To log requests made to GraphQL endpoints, set to true. Default value: false.

Used to filter logs by the URL. If set to /graphql, only GraphQL traffic is logged.

Default value: /graphql.

Defines if logs for GraphQL endpoints store the request’s HTTP headers. To log headers, set the value to true.

Default value: false.

Defines if logs for GraphQL endpoints store the request’s payload. To log payloads, set the value to true.

Default value: true.

Sets the maximum length of the request’s payload expressed in characters. When the request’s payload exceeds this number, the payload is truncated and logs store only the characters within the limit.

Default value: 10000.

Defines if logs for GraphQL endpoints store the query string parameters sent with the request. To log query string parameters, set the value to true.

Default value: true.

Defines if logs for GraphQL endpoints store information about the client that made the request. To log client information, set the value to true.

Default value: true.

A list of HTTP headers that are masked in the logs. This is used to prevent leaking sensitive data, such as authentication tokens.

Default value: host,authorization.

Configures the logging level for GraphQL requests and responses. To enable logging, must be set to DEBUG.

Enables introspection in GraphQL. When enabled, the introspection can be allowed for users (configured based on the type of user and role) and for headers.

At least one user or header configuration must match for introspection to be allowed. See the following introspection properties for the configuration options.

Default value: false.

Defines the type of user that can use introspection in GraphQL.

You can set this property to one of the following options:

Defines which roles can use introspection in GraphQL if the introspection.users property is set to users=MATCHING_ROLES. For example, ataccama.one.mmm.api.introspection.roles=MMM_admin.

Defines the headers under which introspection is allowed for a specific request. Note that configuring headers typically requires that the user cannot specify the header (stripped by ingress). For example, ataccama.one.mmm.api.introspection.headers=X-Allow-Introspection.

If set to true, GraphQL requests are logged in the MMM log. This is useful for debugging purposes and includes requests with sensitive information, such as passwords and secrets.

Enables logging query parts. Applies only if GraphQL requests are logged as well (ataccama.one.mmm.api.logging.request=true).

Enables logging query variables. Applies only if GraphQL requests are logged as well (ataccama.one.mmm.api.logging.request=true).

Enables logging the operation names. Applies only if GraphQL requests are logged as well (ataccama.one.mmm.api.logging.request=true).

If set to true, GraphQL responses are logged in the MMM log. This is useful for debugging purposes and includes responses with sensitive information, such as passwords and secrets.

Enables logging result parts. Applies only if GraphQL responses are logged as well (ataccama.one.mmm.api.logging.response=true).

Enables logging the stack trace if an exception is thrown. Applies only if GraphQL responses are logged as well (ataccama.one.mmm.api.logging.response=true).

A regular expression pattern used for masking sensitive information in MMM logs related to GraphQL. When there is a match, that field is redacted from the GraphQL request or response.

If set to true, metrics are calculated per GraphQL request.

Default value: false.

If set to true, collecting metrics is required for GraphQL annotation.

Default value: true.

Determines whether fields are measured. Can be overridden in GraphQL annotation unless it is disabled. Possible values: enabled (all fields are measured), disabled (fields are not measured).

Default value: disabled.

If set to true, the GraphQL Prometheus metric is exposed to the actuator.

Default value: true.

A cron expression used to schedule user synchronization between Keycloak and MMM. Disabled by default (-).

Cron expressions in Spring format use six space-separated fields representing the following: second, minute, hour, day of the month, month, and day of the week. For example, to run the synchronization every day at midnight, set the property to 0 0 0 ? * *. For more information, see CronExpression documentation.

Default value: -.

Configures the minimum period of time between two user synchronization attempts. If user synchronization is invoked immediately after the previous synchronization, the second invocation is skipped as it is considered unnecessary.

Default value: 2m. For a full list of accepted units, see Duration units.

Enables user synchronization with the identity provider (IDP) on application startup.

Default value: true.

Defines how user synchronization is handled after migrating from one instance of Keycloak to another. By default, users are synchronized by the Keycloak identifier. However, new identifiers are assigned after migration.

The following options are available for merging users:

Default value: PERSON_UNIQUE_USER_ID.

The initial number of threads in the flow event handler thread pool.

Default value: 2.

The maximum number of threads in the flow event handler thread pool. New threads are spawned only when the queue size exceeds its capacity.

Default value: 5.

The number of tasks that the flow event handler thread pool queue can contain. New threads are added only if the queue size is greater than this threshold. If no new threads can be created, the event handler can be rejected.

Default value: Integer.MAX_VALUE.

The number of threads used for processing external events.

Default value: 4.

Configures how often old subscriptions are checked for and deleted.

Default value: 10m. For a full list of accepted units, see Duration units.

Defines for how long offline subscriptions are retained.

The longer the period, the more historical events are stored, which allows clients to occasionally reconnect. On the other hand, retaining a large number of one-time subscriptions that have not been fully unsubscribed increases the amount of data kept in the internal database.

Default value: 72h. For a full list of accepted units, see Duration units.

The maximum number of subscribers that can be registered simultaneously. When the limit has been reached, new subscriptions are automatically rejected.

Default value: 1000.

The number of events that can be stored for each subscriber. Once the limit is reached, the oldest events are discarded.

Default value: 1000000.

The initial number of threads in the scheduler thread pool.

Default value: 5.

The maximum number of threads in the scheduler thread pool. New threads are spawned only when the queue size exceeds its capacity.

Default value: 10.

The number of tasks that the executor queue can contain. New threads are added only if the queue size is greater than this threshold. If no new threads can be created, jobs can be rejected.

Default value: 10.

The version of components that MMM generates for ONE Desktop. Used in component rules, virtual catalog items, monitoring and post-processing plans.

Default value: 13.0.0.devel.

Enables auditing.

A JDBC connection string pointing to the database where audit logs are stored.

Default value: jdbc:postgresql://localhost:5432/audit.

The username for the audit database.

Default value: one.

The password for the audit database.

Default value: one.

The URL or the hostname where the SMTP server is running.

Default value: localhost.

The port where the SMTP server is running.

Default value: 5025.

The username for the SMTP server.

Default value: smtp-user.

The password for the SMTP server.

Default value: smtp-pass.

Enables authentication on the SMTP server.

Default value: false.

Enables TLS authentication on the SMTP server.

Default value: false.

The sender address.

Default value: noreply@ataccama.com.

The base URL for generating links in emails.

Default value: http://localhost:8020.

Must be set to true to enable email notifications.

Default value: false.

The IP address or the hostname of the server where the Anomaly Detector microservice is running.

Default value: localhost.

The number of the gRPC port where the Anomaly Detector microservice is running.

Default value: 8547.

Defines how often the Anomaly Detection plugin checks the queue for new anomaly detection jobs.

Default value: 3s. For a full list of accepted units, see Duration units.

Configures after which amount of time a request sent to the Anomaly Detector expires.

Default value: 3s. For a full list of accepted units, see Duration units.

Enables collecting metrics on Anomaly Detection.

Default value: true.

The maximum number of threads that can be used for storing anomaly detection results.

Default value: 5.

The minimum number of threads that need to be kept alive at all times. These threads are dedicated only to storing anomaly detection results.

Default value: 2.

The number of threads used for scheduled processing of anomaly detection queues.

Default value: 3.

The maximum number of profiles on which anomaly detection can run.

Default value: 100.

The minimum number of profiles on which anomaly detection is run. In case the total number of available profiles is lower than or equal to this value, anomaly detection is skipped.

Default value: 2.

Defines for how long the plugin waits for the response streams from the Anomaly Detector to finish before the job fails.

Default value: 40s. For a full list of accepted units, see Duration units.

If set to true, Term Suggestions are enabled.

Default value: true.

The IP address or the hostname of the server where the Term Suggestions microservices are running.

Default value: localhost.

The number of the gRPC port where the Term Suggestions microservices are running.

Default value: 8544.