Migration to 4.5.x (Nexeed IAS 2025.01.00.x)

Automatic migration of deviation notifiers to Rules

After upgrading to version 4.5.x, the Deviation Notifier navigation element and tab will be removed. However, the functionality will be retained through a new flag (Publish Deviation) in the rule details view. Existing Deviation Notifiers will be automatically migrated to Rules if a matching rule exists at the rule-service-app startup, ensuring that deviation notifications continue to be created as before. If a Deviation Notifier does not have a matching rule, which means they are existing for machine messages, a "Hit of Event" Rule will be created to ensure deviation notifications continue as before.

If an error appears in the logs of rule-service-app similar to the example below, it indicates that the migration was not successful for the tenant, and the Deviation Notifiers were not migrated to Rules for this tenant.

log example: "Error occurred while migrating deviation notifiers for tenant: <TENANT_ID>"

The migration state can also be checked in the new table CM_RM40_DEVIATION_RULE_MIGRATION for each tenant.

If the migration of a tenant fails, you can trigger the migration again by following these steps:

Delete the entry with the name "migrateDeviations" from the CM_RM99_SHEDLOCK table in the database.
Restart one of the rule-service-app pods.

If the migration still fails, please inform the developer team about this issue.

Deletion of deviation notifier resources from MACMA

Because of the removal of the Deviation Notifier functionality from Condition Monitoring we also need to remove the static and dynamic resources of deviation notifier from macma. If an error appears during the deletion of the resources, this can be seen in the logs of the condition-monitring-core. This indicates that the migration was not successful and the resources need to be deleted manually for a specific tenant.

log example: "Error occurred while deleting static deviation notifier resources for tenant: <TENANT_ID>"
log example: "Error occurred while deleting dynamic resources of deviation notifier for tenant: <TENANT_ID>"

If this happens you can first trigger the migration again. Therefore:

Delete from Database CM_CORE99_SHEDLOCK the entry with the name "cm_core_delete_macma_deviation_resources"
Restart one of the condition monitoring core pods

If after that the dynamic or static resources are still not deleted please manually delete them.

For manual deletion please look inside the api documentation of the macma team. From the tenant where the error occurred all dynamic resources with the type:

urn:com:bosch:bci:cm:dynamic:deviationNotifier

need to be deleted.

If there was an error with static resources for a specific tenant please delete those manually. They are having the following ids:

$condition.monitoring.deviation.notification.unassigned.devices
$condition.monitoring.deviation.notifier.view

Helm chart version 2.4 - open telemetry integration

Elastic APM has been replaced with OpenTelemetry (OTEL). For detailed configuration instructions, refer to Chapter "11.5. OpenTelemetry Integration" in the central NEXEED Industrial Application System Operations Manual.

Condition Monitoring switched to the newest Helm Chart Version 2.4 This version includes the following changes:

Open Telemetry is configured globally. If no special configuration is needed, it is enough to configure
- cm.local.observability.otelAutoInjectEnvParams: true
Old configuration parameters need to be removed
- cm.local.otel.loggingLevel
- cm.local.otel.logsExporter
- cm.local.otel.metricsExporter
- cm.local.otel.tracesExporter
- cm.local.otel.exporterOtlpProtocol
- cm.local.otel.tracesSampler
- cm.local.otel.tracesSamplerArg
If needed the global configuration can be overwritten. Following parameters are available:
- cm.local.observability.otelAutoInjectEnvParams
- cm.local.observability.otelLoggingLevel
- cm.local.observability.otelLogsExporter
- cm.local.observability.otelMetricsExporter
- cm.local.observability.otelTracesExporter
- cm.local.observability.otelExporterOtlpProtocol
- cm.local.observability.otelTracesSampler
- cm.local.observability.otelTracesSamplerArg
Swagger UI Parameter was replaced:
- previous: cm.local.swaggerUiEnabled
- now: cm.local.swaggerEnabled

User manual injection into Rule Management

For details please check the user-manual-rule-management-injection.