Release 10.10.0.12
This release upgrades the Apama-ctrl microservice to use Apama 10.7.2.9 (which is the same as Apama 10.7.0 Fix 34).
Fixes
Component | Description | Issue |
---|---|---|
Apama-ctrl microservice | 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-3251 |
Release 10.10.0.11
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
Component | Description | Issue |
---|---|---|
Apama-ctrl microservice | Spring Framework has been upgraded to 5.2.20 to resolve security vulnerabilities CVE-2022-22965. | PAB-3084 |
Release 10.10.0.10
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
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-2981 |
Release 10.10.0.9
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
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-2924 |
Release 10.10.0.8
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
Component | Description | Issue |
---|---|---|
Apama-ctrl microservice | Custom branding is now immediately loaded when you start the Streaming Analytics application. Therefore customized logos will now appear instead of the default logo. | PAB-2815 |
Apama-ctrl microservice | Startup of the Apama-ctrl microservice for tenants with many devices could be slow, which resulted in the hosting platform to assume the instance to be unhealthy and therefore to restart it. The startup time has now been improved by moving expensive queries out of the critical path. | PAB-2827 |
Release 10.10.0.7
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
Component | Description | Issue |
---|---|---|
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-2720 |
Apama Starter microservice | For the Apama Starter microservice, you can now customize the text on the support link that is shown when you click the info icon on the home screen of the Streaming Analytics application, next to "Starter". For more information on customization, see Customizing the home screen of the Streaming Analytics application in the Streaming Analytics guide. | PAB-2735 |
Release 10.10.0.5
Fixes
Component | Description | Issue |
---|---|---|
Analytics Builder, EPL Apps, and smart rules | Text messages (SMS) that were sent from analytic models, EPL apps or smart rules were incorrectly rejected when the sender or recipient addresses contained the protocol identifier "tel". This has now been resolved. | PAB-2656 |
Release 10.10.0.4
Fixes
Component | Description | Issue |
---|---|---|
Apama-ctrl microservice | Startup of the Apama-ctrl microservice for tenants with many devices could be slow and consume excessive memory. This has now been resolved. | PAB-2632 |
Release 10.10.0.3
Fixes
Component | Description | Issue |
---|---|---|
Apama-ctrl microservice | A defect existed in which safe mode was sometimes incorrectly triggered after a platform upgrade, resulting in all user EPL, analytic models and extensions being disabled. This has now been resolved. For more information on safe mode, see Safe mode on startup in the Streaming Analytics guide. | PAB-2602 |
Release 10.10.0
Apama correlator version
This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.7.2 correlator. See also What’s New In Apama 10.7.2 in the Apama documentation.
Improvements for time zone support
In smart rules (and also in the Text Substitution block, see below), it is now possible to specify a time zone for #{time}
substitutions, in the format #{time:TZ=America/New_York}
.
See also Cockpit > Smart rules collection in the User guide.
You can now use a tenant option to set the time zone used for on all at
timers. To set the tenant option, specify the microservice.runtime
category and the timezone
key.
This tenant option is only read when the microservice starts. If the tenant option is changed, the microservice only picks this up on the next microservice subscription.
See also Advanced features > Listeners in the Streaming Analytics guide.
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:
-
An issue which prevented connecting
any
type outputs to blocks which takefloat
as input has been fixed. The Expression block has also been updated to handleany
type inputs. -
The Pulse block now has a new Mode parameter. Its default reflects the block’s previous behavior: it sends a pulse when the value changes. Using this new parameter, you can now configure the block to send a pulse on every input or on every non-zero value. See also Type conversions in the Analytics Builder documentation.
-
The Text Substitution block now supports time zone values. You can now specify a
:TZ=<timezone>
suffix to use a different time zone, for example,#{time:TZ=America/New_York}
to use the time zone for New York. -
The Property Name parameter of the Extract Property block has been renamed to Property Path as it also accepts a path. This is only a label change. You do not need to change existing models. They will continue to work as before.