Streaming Analytics

Release 10.9.0.14

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.7 (which is the same as Apama 10.7.0 Fix 32).

Fixes

Release 10.9.0.13

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.5 (which is the same as Apama 10.7.0 Fix 30).

Fixes

Release 10.9.0.12

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.4 (which is the same as Apama 10.7.0 Fix 29).

Fixes

Release 10.9.0.11

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.3 (which is the same as Apama 10.7.0 Fix 28).

Fixes

Release 10.9.0.10

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.2 (which is the same as Apama 10.7.0 Fix 27).

Fixes

Release 10.9.0.8

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.1 (which is the same as Apama 10.7.0 Fix 26).

Fixes

Release 10.9.0.7

Fixes

Release 10.9.0.6

This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.0 (which is the same as Apama 10.7.0 Fix 25).

Fixes

Release 10.9.0.3

This release upgrades the Apama-ctrl microservice to use Apama 10.7.1.2 (which is the same as Apama 10.5.0 Fix 23).

Release 10.9.0

Apama correlator version

This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.7.1 correlator. See also What’s New In Apama 10.7.0 and What’s New In Apama 10.7.1 in the Apama documentation.

New Streaming Analytics application

A new application called Streaming Analytics is now available in the Cumulocity IoT application switcher. The Apama Analytics Builder and Apama EPL Apps applications from previous versions are now part of this new Streaming Analytics application. See the description of the new application’s home screen for more information.

The Streaming Analytics application supports the standard user interface languages of Cumulocity IoT. See also Available languages in the User guide.

Improvements in alarms generated by the Apama-ctrl microservice

The following improvements are available in this release:

• eplapp_restore_timeout
  This is a new alarm type which is raised if restoring an EPL app on a restart of the Apama-ctrl microservice takes a long time and exceeds a defined time limit. See EPL app restore timeout on restart of Apama-ctrl for more information.

Improvements for sender name and address in SMS messages

Smart rules and EPL apps now pick up the tenant options messaging/sms.senderName and messaging/sms.senderAddress to set the sender name and address values used for SendSMS events. In your EPL apps, you can override the tenant options by specifying senderName and senderAddress in the extraParams field of the SendSMS event.

Note that the tenant options are only read when the Apama-ctrl microservice is started. If the tenant options are changed, you must restart the microservice for the new values to take effect. If these tenant options are not defined, the following system default values are used: “Apama” as the sender name and “apama” as the sender address.

Improvements in EPL apps

New EPL samples are now available from the EPL editor:

• Send an Email, an SMS and an Operation on receiving an Alarm
• Raise an Alarm if no Measurements are received for a user-specified period
• Raise an Alarm if a device leaves the geofence and clear it if it re-enters
• Raise an Alarm if a Measurement exceeds a threshold value

They are similar in behavior to the following frequently-used smart rules:

• On alarm escalate it
• On missing measurements create alarm
• On geofence create alarm
• On measurement threshold create alarm

See Cockpit > Smart rules collection in the User guide for more information on these smart rules.

Improvements in Analytics Builder

The documentation for Analytics Builder, including release notes, is available separately. For your convenience, the release notes from the above documentation are also given below:

• A new application called “Streaming Analytics” is now available in the Cumulocity IoT application switcher. Analytics Builder is now part of this new Streaming Analytics application, together with EPL Apps. See also Starting Analytics Builder.

• The following new blocks are now available:

  • Smart rule behavior:
    • KPI (this block implements the core part of the “On measurement threshold create alarm” smart rule; see also Cockpit > Smart rules collection in the User guide)
    • Text Substitution (see also Cockpit > Smart rules collection > Smart rule variables in the User guide)
  • Position and geofence support:
    • Position Input (new block type for the input blocks)
    • Geofence
  • Non-device inputs and outputs (see also the “On alarm send SMS” and “On alarm send email” smart rules under Cockpit > Smart rules collection in the User guide):
    • Constant Value (see also the list of new input and output ports on existing blocks below)
    • Cron Timer
    • Send SMS
    • Send Email
  • More calculations and aggregates:
    • From Base N
    • To Base N
    • Limit
    • Range
    • Discrete Statistics (see also Details of Values and Blocks)
    • Group Statistics
  • Utilities and flow manipulation to give more flexibility in writing models:
    • Duration
    • Set Properties (see also the list of new input and output ports on existing blocks below)
    • Selector
    • Switch (this block is intended to be used with template parameters)

  See the Block Reference for detailed information on the new blocks.

• Additions and changes to existing blocks:

  • Managed Object Input:
    • The Property Name parameter is now optional. If not set, any update to a managed object generates an output.
  • Managed Object Output:
    • The Property Name parameter is now optional, allowing several properties to be updated in one go (for example, using the new Set Properties block).
  • Event Output:
    • New Time input port.
    • New Properties input port (see also the new Set Properties block).
  • Operation Output:
    • New Properties input port (see also the new Set Properties block).
  • Alarm Output:
    • The Severity parameter is now optional. The severity of the alarm can now be set either via the Severity parameter or the new Severity input port. One of the input port and parameter must be connected or set.
    • The Severity input port (but not parameter) also supports a CLEARED value to clear the alarm instead of creating or changing the severity of an existing alarm.
    • The Message parameter is now optional. The message of the alarm can now be set either via the Message parameter or the new Message input port. One of the input port and parameter must be connected or set.
    • New Time input port.
    • New Clear Alarm input port.
  • Extract Property:
    • The Property Type parameter now supports a new option: Properties. This is intended to be used with the following block types: Operation Output (the Properties input port), Event Output (the Properties input port), and Managed Object Output (the Value input port).
    • The Property Name parameter is now optional so that the Properties Type is able to just pass through the properties (see also the new Set Properties block).

  See the Block Reference for detailed information on the above changes.

• The input blocks are now able to distinguish between create and update events. For this purpose, a new Notification Mode parameter is now available in the block parameter editor. This is helpful, for example, if you are only interested in new alarms being created and you are not interested in models being activated when the same alarm is updated. This new parameter is available for the input blocks of type Alarm Input, Event Input, Operation Input, and also for the new Position Input type. It is not available for input blocks of type Measurement Input as measurements cannot be updated. See the Input category in the Block Reference for more information.

• A new chain_diagnostics parameter for monitoring periodic status is now available. It provides diagnostic information about model chains, such as the time when the chain was created or the number of times the chain has been evaluated. See Monitoring periodic status for more information.

• A new block_promise_timeout_secs key for configuring model timeouts is now available. This tenant option defines the timeout in seconds to wait for Promise values returned by block actions like $validate to be completed. The default is 60 seconds. See Keys for model timeouts for more information.

• Objects containing the c8y_Kpi property are now treated as broadcast devices in addition to pas_broadcastDevice. See Broadcast devices for more information.

• Analytics Builder now supports the standard user interface languages of Cumulocity IoT. See Available languages in the User guide for more information.

• Detailed documentation is now available which covers the distinctions between value types representing continuous-time and discrete-time values, and the pulse type. It also covers some of the details of block implementations around windowing and when blocks generate output. See Details of Values and Blocks.