Diese Seite ist nur auf Englisch verfügbar.

Start and shutdown

Condition Monitoring and Rules Management services are computed to docker images: condition-monitoring-core, rule-service-app, rule-function-executor, rule-result-aggregator, rule-value-aggregator, rule-value-provider or if rules light is enabled stateful-function-executor. For Azure environments the docker images are handled by Kubernetes.

To certify that Condition Monitoring and Rules Management application is started or not you should use the health check endpoint response: if the response status code is 200 and health_response.health == 'healthy' then services are started and healthy.

Start

Automated setup of database tables

Condition Monitoring and Rules Management checks on startup if the database contains all required tables. If not existing, Condition Monitoring automatically creates or updates the tables on startup. As long as the table setup or update is running, the health state of the 'cm/condition-monitoring-core' is not in state "ready".

Automated setup of messaging queues

Condition Monitoring and Rules Management checks on startup if the required message queues are available. If not existing, Condition Monitoring automatically creates or updates the necessary queues. As long as the setup or update is running, the health state of the 'cm/condition-monitoring-core' is not in state "ready".

Verify correct startup via health endpoints

In order to verify that the Condition Monitoring application has started correctly, the health check endpoint can be used. If the response status code is 200 and health_response.health == 'healthy' then services successfully started.

Shutdown

Decommissioning cm

Set the variable 'enabled' in HELM’s 'custom-values.yaml' file to 'false' in case you want to decommission CM from your IAS installation. Here is an example file for further illustration:

cm:
  enabled: true
  ruleManagementLightEnabled: true
Edit this pageDiese Seite bearbeiten

Feedback on this pageFeedback zu dieser Seite