Streaming Analytics

Release 10.15.0.9

This release upgrades the Apama-ctrl microservice to use Apama 10.15.3.1 (which is the same as Apama 10.15 Fix 12).

Fixes

Release 10.15.0.8

This release upgrades the Apama-ctrl microservice to use Apama 10.15.0.10 (which is the same as Apama 10.15.2.4).

Fixes

Release 10.15.0.7

This release upgrades the Apama-ctrl microservice to use Apama 10.15.0.9 (which is the same as Apama 10.15.2.3).

Fixes

Release 10.15.0.6

This release upgrades the Apama-ctrl microservice to use Apama 10.15.0.7 (which is the same as Apama 10.15.2.1).

Fixes

Release 10.15.0.5

This release upgrades the Apama-ctrl microservice to use Apama 10.15.0.3 (which is the same as Apama 10.15.1.0).

Fixes

This release does not contain any fixes.

Release 10.15.0.4

In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.15.0.3 release.

Fixes

Release 10.15.0.3

This release upgrades the Apama-ctrl microservice to use Apama 10.15.0.2.

Fixes

Release 10.15.0

Apama correlator version

This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.15.0 correlator. EPL apps developers should also refer to What’s New In Apama 10.15.0 in the Apama documentation.

Improvements for multi-tenancy

Apama applications can now work in a multi-tenant manner when used in a custom microservice. See also the information on running and testing the monitor file in Developing apps with Software AG Designer and the required settings in the microservice manifest in Deploying Apama applications as microservices, both in the Streaming Analytics guide.

Improvements for requests with concurrent connections

In order to provide better performance for requests to the Cumulocity IoT platform, Streaming Analytics now uses multiple client connections to perform requests concurrently. You can adjust the default number of connections using the client.numClients tenant option in the streaminganalytics category. See also Optimizing requests with concurrent connections in the Streaming Analytics guide.

The new concurrent connection capability provides improved performance for all smart rules, Analytics Builder models and EPL apps that were previously restricted in performance because they had to wait for other, unrelated, Streaming Analytics requests to complete before they could make their own requests.

Info: This does not apply to the Apama-ctrl-smartrules and Apama-ctrl-smartrulesmt microservices. They have a fixed value of 1 (that is, fully serial) for this option, which is not configurable.

Improvements for hiding the version information

It is now possible to hide the version information that is by default shown at the bottom of the Streaming Analytics home screen and the Analytics Builder (model manager) and EPL Apps (EPL app manager) pages. You can do this by setting the hidePowered application option to true. If this option is not set or set to false, the version information is shown at the bottom of these pages. See also Branding and language customization in the Web SDK guide.

Improvements for customizing the documentation links

It is now possible to customize all of the documentation links that are shown in the Streaming Analytics application so that they point to a different website. You can do this by setting the following new properties at the top of the documentation.json file to different base URLs:

• apamaWebHelpBaseLink
• analyticsBuilderWebHelpBaseLink
• cumulocityGuideBaseLink

See also Customizing the home screen of the Streaming Analytics application in the Streaming Analytics guide.

Improvements in Analytics Builder

Additional Analytics Builder samples are now available in the model editor. The provided samples now cover all of the smart rules from Cumulocity IoT.

Detailed descriptions have been added for the Analytics Builder samples. You can see the first lines of such a description in a tooltip when you move the mouse over the card for a sample, or you can see the full description when you view a sample (or create a model from the sample) and then open the Model Configuration dialog box.

It is now possible to search for Analytics Builder samples with specific words in their names and to filter them by tags.

In the previous release, the template parameter names in the Analytics Builder samples were only available in English. As of this release, translations are available for the supported languages.

The Alarm Output and Measurement Output blocks now have a new Params Fragment parameter and a new Properties input port. These can be used to set custom properties, similar to the already existing functionality of the Event Output block.

The Alarm Output block now has a new Create Asynchronous Output parameter. It is not selected by default which reflects the block’s previous behavior. When selected, alarms can now be created and cleared asynchronously.

Caution: The default behavior of the Alarm Output block is to produce a synchronous output and the Analytics Builder framework explicitly disallows models that can cause a loop when synchronous outputs are produced. However, such validations are disabled when asynchronous outputs are being produced. Therefore, special care must be taken when using the Create Asynchronous Output parameter. This may result in infinite loops during model execution (for the same model or across multiple models), leading to performance degradation or the application running out of memory. For example, a loop can occur if the model consumes an alarm input of type <foo> and produces an alarm output of type <foo> for the same device; the output generated by the model is then again consumed by the same model as an input, resulting in a loop.

Analytics Builder now supports the globalTitle branding option for the category names in the model editor. See also Branding and language customization in the Web SDK guide.

Fixes