cm/condition-monitoring-core

The URL of the CM installation. e.g. http://localhost/cm

Yes

-

Environment Variable

Condition Monitoring service port

No

8080

Environment Variable

Maximum direct memory size for JVM, controlling the amount of off-heap memory available for direct byte buffers used in NIO operations, network communications, and memory-mapped files

No

128m

Environment Variable

Stack size for JVM threads

No

512k

Environment Variable

Maximum percentage of available RAM that the JVM heap can use

No

60.0

Environment Variable

Sets the log level for security logger

No

INFO

Environment Variable

Sets the log level for life cycle logger

No

INFO

Environment Variable

Flag to enable Swagger UI

No

false

Environment Variable

Condition Monitoring application instance id

Yes

-

Environment Variable

Activates the AI module

No

true

Environment Variable

Activates the deviation processor

No

false

Environment Variable

List of tenant ids for which machine messages should be forwarded as deviations. Value is comma seperated tenantId list e.g. 7311ea8c-5d48-43fe-acf9-980eedf24b6c,5ce47434-c412-4e8c-8482-0ce1df556493

No

-

Environment Variable

Timeout in ms for Condition Monitoring batch messaging

No

200

Environment Variable

Max size for Condition Monitoring batch messaging

No

200

Environment Variable

How often in milliseconds the ACL-Reload-Scheduler will be run.

No

90000

Environment Variable

Flag indicating whether the scheduler to reload the device master data from MDM should be enabled. When it is activated, it is reloading every sunday 2 am UTC.

No

false

Environment Variable

Number of maximal attempts in case of error occurred during consumption of message

No

10

Environment Variable

The URL of the Portal registration endpoint

Yes

-

Environment Variable

The MACMA application id of Condition Monitoring.

Yes

cm

Environment Variable

The application secret of Condition Monitoring in MACMA.

Yes

-

Environment Variable

Driver class of the database. Prefix is optional, so that database can be configured globally.

Yes

-

Environment Variable

JDBC URL of the database. Prefix is optional, so that database can be configured globally.

Yes

-

Environment Variable

User for the database.

Yes

-

Environment Variable

Password for the database.

Yes

-

Environment Variable

Number of maximum pool size for the database connection.

No

5

Environment Variable

Flag for changing the durability x.cm.ruleResult.positive exchange. When CPM and CM installed at the same time, then it needs to be set to false to make this exchange non-durable, otherwise cpm will have startup problem.

No

true

Environment Variable

Maximum amount of data points which will be responded to the client for the actual value.

No

7500

Environment Variable

Maximum amount of data points which will be responded to the client for the target.

No

500

Environment Variable

Maximum amount of data points which will be responded to the client for the upper error.

No

500

Environment Variable

Maximum amount of data points which will be responded to the client for the upper warn.

No

500

Environment Variable

Maximum amount of data points which will be responded to the client for the lower warn.

No

500

Environment Variable

Maximum amount of data points which will be responded to the client for the lower error.

No

500

Environment Variable

The block size will be incremented for every decimation step

No

2

Environment Variable

The block size where the decimation starts with

No

3

Environment Variable

Maximum number of Influx records to protect Influx and avoid OOM.

No

1000000

Environment Variable

Average amount of points loaded from Influx with one query. Decreasing this value will lead to more parallel queries, which might have a better performance for the full load. tradeoff: Response-Time of Influx queries vs. sub-result-joining (as preparation for decimation on one large DataPointSet)

No

8000

Environment Variable

Average amount of points loaded from Influx with one query per chunk.

No

8000

Environment Variable

limit indicates cutoff, at which timeframe-adjustment will be performed. Will also limit the maximum number of records queried from Influx.

No

225000

Environment Variable

Execute the detection and publishing of unknown measuring points with a fixed period between the end of the last invocation and the start of the next.

No

60000

Environment Variable

Comma-separated list of Facility Type IDs (e.g., IAS Production Area, MES Area) for which dynamic resources should be registered. Multiple Facility Type IDs can be combined to enable Fine-Grained Access for several topology levels simultaneously, e.g. E14CAB2A-2113-441C-A4A1-FCC6AF91861D,F2BFFBF3-1113-4F99-81BC-C782458AD8A2. Each tenant can have its own list by defining the variable: CMCORE_FACILITYTYPESTOREGISTERRESOURCE_{{REPLACE_HERE_WITH_YOUR_TENANT_ID}} e.g. CMCORE_FACILITYTYPESTOREGISTERRESOURCE_7311ea8c-5d48-43fe-acf9-980eedf24b6c. If the tenant-specific variable is defined, only that list will be used. For detailed configuration instructions, see Fine-Grained Access Configuration.

No

-

Environment Variable

Codes are not tags but fields. So a machine message is unique by timestamp, tenant and device. Two machine messages with the same timestamp, tenant, device and code override each other. The solution is to add randomness to the timestamp.

No

True

Environment Variable

Influx machine message has an unique upper bound of specified value.

No

10000

Environment Variable

Maximum amount of raw events which will be responded to the client.

No

1000

Environment Variable

limit indicates cutoff, at which timeframe-adjustment will be performed. Will also limit the maximum number of records queried from Influx.

No

225000

Environment Variable

Average amount of points loaded from Influx with 4x3 (|severity| * |source|) queries within nested loops. Decreasing this value will lead to more parallel queries, which might have a better performance for the full load.

No

60000

Environment Variable

The url of the Influx database.

Yes

-

Environment Variable

The username of the Influx database user.

Yes

-

Environment Variable

The password of the Influx database user.

Yes

-

Environment Variable

The database name of the Influx database.

No

cm

Environment Variable

The log level for Influx database related communication. Possible values: NONE, BASIC, HEADERS, FULL

No

NONE

Environment Variable

The retention policy replication factor describes how many copies of the inserted data are stored in the cluster. Replication > 1 needs an Influx enterprise license.

No

2

Environment Variable

The retention policy duration describes for how long the Influx database keeps the event (rule result and machine messages) data.

No

180d

Environment Variable

The retention policy duration describes for how long the Influx database keeps the raw measurements data.

No

7d

Environment Variable

The deferred retention policy duration describes for how long the Influx database keeps the raw measurements data.

No

1d

Environment Variable (cm.local.influx.msmDeferredRetentionPolicyDuration)

The retention policy duration describes for how long the Influx database keeps the 1 minute aggregated measurements data.

No

45d

Environment Variable

The retention policy duration describes for how long the Influx database keeps the 30 minute aggregated measurements data.

No

90d

Environment Variable

The retention policy duration describes for how long the Influx database keeps the 12 hour aggregated measurements data.

No

180d

Environment Variable

The retention policy duration describes for how long the Influx database keeps the metadata information (e.g. part type).

No

30d

Environment Variable

The number of actions (data point writes to the Influx database) to collect in batch for event messages.

No

5000

Environment Variable

Size of queue for new events messages that are written before the previous (failed) are successfully written (needs to be larger than the actions in order to use 'Retry on error' strategy).

No

50000

Environment Variable

The number of actions (data point writes to the Influx database) to collect in batch for measurement messages.

No

8000

Environment Variable

Size of queue for new measurements messages that are written before the previous (failed) are successfully written (needs to be larger than the actions in order to use 'Retry on error' strategy).

No

50000

Environment Variable

Execute the backfilling with a fixed delay between the end of the last invocation and the start of the next.

No

300000 (5 minutes)

Environment Variable