Release 10.13.0.6
This release upgrades the Apama-ctrl microservice to use Apama 10.11.3.6 (which is the same as Apama 10.11.0 Fix 13).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | Requests from a user who is logged in using TFA were rejected when Apama-ctrl-smartrules or Apama-ctrl-smartrulesmt microservice backends are used. This issue has now been resolved. | PAB-3652 |
| Apama-ctrl microservice | Requests from a user who is logged in using OAI-Secure were rejected when Apama-ctrl-smartrules or Apama-ctrl-smartrulesmt microservice backends are used. This issue has now been resolved. | PAB-3648 |
| Analytics Builder | When the Create Alarm block was raising a new alarm, there was a chance for duplicate events to be delivered to the worker, causing multiple invocations for the same input. This issue has now been resolved. | PAB-3634 |
| EPL Apps | Performance optimizations have been made which should improve high-throughput measurement use cases. | PAB-3612 |
Release 10.13.0.5
This release upgrades the Apama-ctrl microservice to use Apama 10.11.3.4 (which is the same as Apama 10.11.0 Fix 11).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | There was a bug in which it was possible for a user of the tenant to extract the credentials of the Apama-ctrl microservice and thus escalate privileges within the tenant. This issue has now been resolved. | PAB-3326 |
| EPL Apps | The alignment of the cards on the EPL Apps page was broken in the Streaming Analytics application. This issue has now been resolved. | PAB-3366 |
Release 10.13.0.4
In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.13.0.3 release.
Fixes
| Component | Description | Issue |
|---|---|---|
| Smart rules | cep_proxy_request_counts information in health, prometheus, diagnostics/apamaCtrlStatus responses
and Proxy Status status lines now uses the hostnames of the core nodes instead of IP addresses. |
PAB-3280 |
Release 10.13.0.3
In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.13.0.2 release.
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-3249 |
Release 10.13.0.2
This release upgrades the Apama-ctrl microservice to use Apama 10.11.3.3 (which is the same as Apama 10.11.0 Fix 10).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | Parallel processing of incoming requests now uses the x-core-origin header to distribute incoming requests.
This header is supplied by the Cumulocity IoT platform for incoming requests to Apama.
A new user status metric is provided that indicates the number of measurements processed per channel and which is updated every 10 seconds.
For example: cumulocity.measurement.splitter.1.processed. |
PAB-3077 |
| Apama-ctrl microservice | The Apama-ctrl microservice now uses the recommended mechanism for configuring the security of endpoints instead of using the deprecated mechanism. This fixes Spring's warnings to ask Spring Security to ignore Ant patterns. | PAB-3086 |
| Apama-ctrl microservice | The Apama-ctrl microservice now retries the lookup of the tenant option for the time zone in case of an error during startup, instead of using the UTC time zone. | PAB-3139 |
Release 10.13.0.1
This release upgrades the Apama-ctrl microservice to use Apama 10.11.3.1 (which is the same as Apama 10.11.0 Fix 8).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl-smartrulesmt microservice | An issue has been fixed regarding privilege escalation with diagnostic endpoints. | PAB-3012 |
| Streaming Analytics application | An issue has been fixed regarding the routing for certain paths when using Firefox. | PAB-3019 |
| Analytics Builder | In the German version of the block reference, the link text for the Text Substitution block has been fixed. | PAB-3042 |
| Apama-ctrl microservice | Spring Framework has been upgraded to 5.3.18 and Spring Boot has been upgraded to 2.5.12 to resolve security vulnerabilities CVE-2022-22965. | PAB-3070 |
Release 10.13.0
Apama correlator version
This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.11.2 correlator. EPL apps developers should also refer to What’s New In Apama 10.11.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 define the new FORMAT parameter for specifying a different time format.
For example, #{time:TZ="America/New_York",FORMAT="HH:mm:ssZ"} specifies the time zone for New York and the format to be HH:mm:ssZ.
For a list of valid time format strings, see Format specification for the TimeFormat functions in the Apama documentation.
See also Cockpit > Smart rules collection > Smart rule variables in the User guide.
Improvements in alarms generated by the Apama-ctrl microservice
Substitution variables, specifically time formats and time zones, now have their configuration validated when they are used in smart rules or Analytics Builder. See also Smart rule configuration failed.
Improvements for EPL apps
The EPL samples that can be accessed from the EPL editor of the Streaming Analytics application have been revised to make them more concise and to have a more narrow focus. See also Developing apps with the Streaming Analytics application.
Improvements in Analytics Builder
The Send Email
and Send SMS
blocks can now be used in simulation and test mode.
When running in these modes, these blocks log the output instead of sending an email or SMS.
In previous versions, when using these blocks in simulation or test mode, the activation of the model failed with the following error message:
Model produces output for device '' not declared by any block. Make sure that device parameters of all blocks are properly tagged.
The Text Substitution
block now supports the new FORMAT parameter for specifying a different time format.
For example, #{time:TZ="America/New_York",FORMAT="HH:mm:ssZ"} specifies the time zone for New York and the format to be HH:mm:ssZ.
For a list of valid time format strings, see Format specification for the TimeFormat functions in the Apama documentation.