Streaming Analytics

Release 10.6.6.30

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

Fixes

Component	Description	Issue
Smart rules	When existing smart rules were migrated from CEL (Esper) to Apama, the implementation could create stale instances if a smart rule was edited or deleted after migration. This is resolved now.	PAB-3252

Release 10.6.6.29

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

Fixes

Component	Description	Issue
Apama-ctrl microservice	Apache Log4j inside all variants of the Apama-ctrl microservice has been upgraded to version 2.17.1 to resolve security vulnerabilities CVE-2021-44832 and CVE-2021-45105.	PAB-2984

Release 10.6.6.28

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

Fixes

Component	Description	Issue
Apama-ctrl microservice	Apache Log4j inside all variants of the Apama-ctrl microservice has been upgraded to version 2.16.0 to resolve security vulnerabilities CVE-2021-44228 and CVE-2021-45046.	PAB-2927

Release 10.6.6.27

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

Fixes

Component	Description	Issue
Apama-ctrl microservice	When sending SMS from EPL apps or smart rules, sender or recipient addresses with the protocol identifier "tel" were being incorrectly rejected. This has now been resolved.	PAB-2654
Apama-ctrl microservice	Microservices migrating from version 10.6.6.26 or lower could experience null pointer exceptions in the microservice log files, and a failure to start upon upgrade. This was caused by attempting to read a value from a field that had not existed prior to this version. The microservice will now set default values and not attempt to read the field if it does not exist.	PAB-2702

Release 10.6.6.25

Fixes

Component	Description	Issue
Analytics Builder	The Expression block now supports `Value` and `any` type inputs. These are unpacked to concrete types before evaluating the expression. Note that this means that the Expression block's type checking is lenient now when it comes to these types of inputs. So even when your model passes validation, it might fail at runtime if you are trying to do unsupported operations.	PAB-2467
Analytics Builder	It is now possible to connect a block with an `any` output type to a block with a `float` input type. Previously, this was incorrectly flagged as an error. As with other such conversions, the type of the value is only checked at runtime. If a block actually outputs a string, this may fail if the string does not contain a number.	PAB-2468
Apama-ctrl microservice	The Apama-ctrl microservice now includes the roles ROLE_BULK_OPERATION_ADMIN, ROLE_BULK_OPERATION_READ, ROLE_AUDIT_ADMIN, ROLE_AUDIT_READ, ROLE_TENANT_MANAGEMENT_READ, ROLE_USER_MANAGEMENT_OWN_READ for its service user, which means that EPL apps can make bulk operation requests, audit entries and can read tenant information and its own user information.	PAB-2495

Release 10.6.6.24

Fixes

Component	Description	Issue
Apama-ctrl microservice	An issue has been resolved where in some rare conditions messages from Cumulocity IoT core nodes to Apama may be lost without any alarms being raised.	PAB-2299
Apama Analytics Builder	An issue has been resolved where a model may time out when it is activating, failing to report either success or a failure. This would affect models with a large number of blocks of certain types (mostly input and output blocks) where at least one of the blocks cause the model to fail to activate correctly.	PAB-2305

Release 10.6.6.23

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

Fixes

Component	Description	Issue
Smart rules and EPL apps	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.	PAB-2147

Release 10.6.6.22

In order to maintain compatibility with Esper-hosted smart rules, the “On measurement threshold create alarm” and “On measurement explicit threshold create alarm” smart rules have changed behavior:

The upper value of the red range (the one used for the “On measurement explicit threshold create alarm” smart rule) is now inclusive. Note that the yellow range is still exclusive on the upper value end.
If the red and yellow ranges overlap, the value is treated as “yellow”, that is, MINOR, not CRITICAL severity.

For more information on the above smart rules, see Smart rules in the User guide.

Release 10.6.6.2

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

Fixes

Component	Description	Issue
Apama-ctrl microservice	`onGeofenceCreateAlarm` and `onGeofenceSendEmail` smart rules behaved incorrectly when updates were received without location information. This problem has now been resolved.	PAB-1699

Release 10.6.6

Apama correlator version

This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.5.3 correlator.

Improvements in alarms generated by the Apama-ctrl microservice

The following improvements are available in this release:

lost_correlator_connection
This is a new alarm type which is raised in certain cases when the connection between the Apama-ctrl microservice and the correlator is lost. See Connection to correlator lost for more information.
application_queue_full
This is a new alarm type which is raised whenever the correlator queue is full, including both input and output queues. See The correlator queue is full for more information.
APAMA_CTRL_WARN_<HASHCODE>
This is an enhancement to the existing alarm type. An alarm is now raised when the correlator context is blocked for too long, not letting any other apps run in the same context or, even worse, causes excessive memory usage (as the correlator is unable to perform any garbage collection cycles) leading to the app running out of memory. See An EPL file blocks the correlator context for too long for more information.

New tooling for Apama EPL Apps on GitHub

Tooling to work with Apama EPL Apps has been published at https://github.com/SoftwareAG/apama-eplapps-tools. This tooling allows you to script uploads of your EPL apps and manage them for CI/CD (continuous integration and continuous delivery) use cases. It also provides extensions to the PySys test framework to allow you to simply write tests for your EPL apps and to run them automatically. For more information on PySys, see the API Reference for Python that you can access from the Apama documentation.

Improvements in Apama Analytics Builder

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

The input block type Managed Object Input is now able to output the initial value of the property that is specified by the Property Name parameter when the model is activated. For this purpose, the Capture Start Value check box is now available in the block parameter editor. It is deselected (false) by default. See the Block Reference in the model editor for more information.
The Expression block now allows integers in intermediate results, for example, as the result of a floor() or round() function. If the result of an expression is an integer value, it is converted to a float automatically (there might be a loss of precision). Previously, the Expression block could handle only float, string and Boolean types. See the Block Reference in the model editor for more information.