Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Administative tasks in the IIoT Core Services UI

The following administrative tasks can be performed in the IIoT Core Services UI.

Enable message persistence in the message queue

You can ensure the retention of all data messages in internal routes, even during full or partial system failure, by enabling message persistence in the message queue of AMQP.

With message persistence enabled, messages in internal routes are written to disk. In the event of a system failure, the messages are processed when service is restored. Without message persistence, messages are stored only in memory and can be lost. This feature is enabled by default.

NoteEnabling message persistence can adversely affect system performance, because each message adds a write operation.

Procedure

  1. In the IIoT Core Services UI, select the Administration tab.

  2. Select the Data Routes Configuration tab.

  3. Toggle to turn on Enable internal routes - AMQP persistence.

  4. Click Apply.

Measure message latency

You can measure the average amount of time from when IIoT Core Services receives a message to when it writes the message to the final database, to help you fine-tune your system settings during maintenance. This feature is disabled by default.

The information is stored in the couchdb database. See your system administrator for information about querying couchdb.

NoteHaving performance metrics enabled during production can cause performance degradation.

Procedure

  1. In the IIoT Core Services UI, select the Administration tab.

  2. Select Data Routes Configuration.

  3. Toggle to turn on Enable performance metrics.

  4. (Optional) Enter a value for Data per batch. This is the number of messages grouped to create an average value. The default is 200.

  5. Click Apply.

Count the number of messages received

This feature is disabled by default. Enable message enumeration to record the number of messages received by IIoT Core Services.

Once recorded, compare it with the number of messages sent by the registered asset. Information about the number of messages sent is stored in the couchdb database. See your system administrator for information about querying couchdb.

Procedure

  1. In the IIoT Core Services UI, select the Administration tab.

  2. Select Data Routes Configuration.

  3. Toggle to turn on Number of messages received.

  4. (Optional) Enter a time value for Batch Time. This is the time interval between message counter updates. Increasing the time value minimizes the number of write operations. The default is 5 seconds. To change the default, enter a number followed by a letter indicating a time period, as follows:

    • s = seconds
    • m = minutes
    • h = hours
    • d = days
  5. Click Apply.

Configure log level

You can set the level for the types of messages that are logged.

The default log level is info. Each log level includes logging of the preceding levels. Minimizing the number of messages that are logged improves performance. Set a high level of logging for troubleshooting. The order of log levels from the most to the least amount of logging is as follows:

  • debug
  • info
  • warn
  • error
NoteUnless you are performing maintenance or are troubleshooting, set the log level to info. Consistent high levels of logging can cause the file system to become full with logs.

Procedure

  1. In the IIoT Core Services UI, select the Administration tab.

  2. Select Log Configuration.

  3. Select a log level.

  4. Click Apply.