MDM 16.2.0 Upgrade Notes

Monitoring metrics changes

Starting from 16.2.0, monitoring in MDM is enhanced thanks to the new metrics for data access operations, user configuration tracking, and startup performance monitoring. Additionally, several existing metrics have been updated for consistency and clarity.

This section lists added or updated metrics for references purposes. For complete details, see configuration:monitoring-metrics.adoc.

Added metrics

Data access metrics

Track record processing across four categories: batch operations, publish actions from the web application, online services (REST, SOAP), and streaming platforms (such as Kafka or SQS). Each category contains metrics for input records and final changes categorized by operation type (Insert, Update, Delete).

Batch operations:
- ataccama_one_mdm_batch_records_input_count_total: The number of records that were ever inputted to any batch load operation.
- ataccama_one_mdm_batch_records_changed_count_total: The number of records that were changed by a batch load operation.
Publish operations:
- ataccama_one_mdm_publishing_records_input_count_total: The number of records inputted to publish actions from the web application.
- ataccama_one_mdm_publishing_records_changes_count_total: The number of changed records by publish actions from the web application.
Service (REST, SOAP) operations:
ataccama_one_mdm_services_records_input_count_total: The number of records on input for publish actions from online services (for example, REST, SOAP)
ataccama_one_mdm_services_records_changes_count_total: The number of changed records by publish actions from online services.
Streaming operations:
ataccama_one_mdm_streaming_records_input_count_total: The number of records that were ever inputted to any streaming operation
ataccama_one_mdm_streaming_records_changed_count_total: The number of records changed by streaming operations.

User configuration metrics

ataccama_one_mdm_configured_mda_users_count: The number of configured MDM Web App users, categorized by permission type.

Startup performance metrics

Measure the duration of various application startup phases.

ataccama_one_mdm_startup_total_seconds: The total startup time from the JVM startup until the application context is started.
ataccama_one_mdm_startup_application_context_active_seconds: The time taken for the application context to become active during startup.
ataccama_one_mdm_startup_application_context_seconds: The time taken for the application context startup phase, this includes initialization of beans and other context-related setup.
ataccama_one_mdm_startup_jvm_seconds: The JVM startup time, from the beginning of JVM initialization to the start of the root context.
ataccama_one_mdm_startup_management_context_active_seconds: The time taken for the management context to become active during startup.
ataccama_one_mdm_startup_management_context_seconds: The time taken for the management context startup phase.
ataccama_one_mdm_startup_root_context_seconds: The startup time of the root context.

DQ engine threadpool monitoring

Metrics for monitoring the Data Quality engine thread pool.

ataccama_one_mdm_dqc_threadpool_threads_total: The total number of threads in DQ engine, distinguished by their lifecycle stage.

Changed metrics

The following metrics have been updated for consistency and improved labeling:

User activity metrics*: Label values changed from underscore (_) to camelCase for consistency:
ataccama_one_mdm_active_users_last_day_count: The number of users active in the last 24 hours in MDM Web App. actions label values changed from read_only/read_write to readOnly/readWrite.
ataccama_one_mdm_active_users_last_hour_count: The number of users active in the last hour in MDM Web App. actions label values changed from read_only/read_write to readOnly/readWrite.

DQ engine threadpool

Consolidated from two separate metrics into one with labels:
dqc_threadpool_threads_total: New metric is ataccama_one_mdm_dqc_threadpool_threads_total{type="created"}.
dqc_threadpool_threads_finished_total: New metric is ataccama_one_mdm_dqc_threadpool_threads_total{type="finished"}.

Deleted metrics

The following metrics have been removed as they are replaced by the new data access metrics or are no longer relevant:

ataccama_one_mdm_publishing_daily_changes_count
ataccama_one_mdm_batch_daily_changes_count
ataccama_one_mdm_batch_records_count
ataccama_one_mdm_streaming_average_operation_duration
ataccama_one_mdm_streaming_daily_changes_count
ataccama_one_mdm_streaming_daily_requests_count
ataccama_one_mdm_streaming_records_count

If you have monitoring dashboards or alerts configured using these deleted metrics, update them to use the new data access metrics.

Changes in REST API permissions

New security permissions were added, allowing you finer control over which users can write to which records. We recommend reviewing your security permissions and updating them accordingly.

WriteInstanceLayer permission: Grants permission to write all instance records across all entities and source systems.
WriteMasterLayer permission: Grants permission to write all master records Supports optional master view restrictions.

In addition, WriteEntities permissions was modified to support both instance and master entities, instead of only instance entities. For backward compatibility, when no layer is specified, the entity is treated as an instance entity. This allows existing configurations using instance entities to continue to function as before.

Configuration changelog

This section provides information about the changes in the configuration files that need to be taken into account when upgrading the solution.

The following table lists the configuration files that were added, changed, or removed.

Added files	Changed files	Removed files
/	nme-security.xml	/

Added files

Changed files

Removed files

nme-security.xml

Changed properties

The following security configuration options have been added or modified:

WriteInstanceLayer - New permission for instance layer write access.

Sample configuration

<permission class="com.ataccama.nme.engine.security.auth.permissions.WriteInstanceLayer" />

WriteMasterLayer - New permission for master layer write access with optional view restrictions.

Sample configuration

<!-- Permission to write all master records -->
<permission class="com.ataccama.nme.engine.security.auth.permissions.WriteMasterLayer" />

<!-- Permission to write master records only in specific views -->
<permission class="com.ataccama.nme.engine.security.auth.permissions.WriteMasterLayer">
  <masterViews>
    <view>master</view>
    <view>master_restricted</view>
  </masterViews>
</permission>

WriteEntities - Enhanced to support both instance and master entities with layer-specific configuration.

Extended configuration with both instance and master entities:

<permission class="com.ataccama.nme.engine.security.auth.permissions.WriteEntities">
  <entities>
    <entity name="contact" layer="instance" />
    <entity name="party" layer="master" masterView="master_restricted" />
  </entities>
</permission>

Was this page useful?