Release 10.14.0.6
This release upgrades the Apama-ctrl microservice to use Apama 10.11.3.7 (which is the same as Apama 10.11 Fix 14).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | For security reasons, ROLE_APPLICATION_MANAGEMENT_ADMIN and ROLE_OPTION_MANAGEMENT_ADMIN have been removed from the required roles which are defined in the manifest file of the Apama-ctrl microservice. Any applications deployed with the Streaming Analytics application (for example, EPL apps) can no longer perform security-sensitive operations such as application creation or modification of tenant options. | PAB-3689 |
| Analytics Builder | The Alarm Output block in Analytics Builder no longer reactivates "Acknowledged" alarms with every modification. Acknowledged alarms are only reactivated if the severity has increased. This also ensures that the alarm count is updated correctly. | PAB-4027 |
| Analytics Builder | The Expression block now calculates the remainder of integer division, as already documented. Previously, this functionality was not implemented and raised a runtime error if defined. | PAB-4106 |
| Analytics Builder | Deploying a model in test mode and then undeploying it could fail and could cause failures for other model deployments if another model with the same output blocks was already deployed in production mode and formed a chain with another already deployed model. This issue has now been resolved. | PAB-3664 |
Release 10.14.0.5
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-3653 |
| 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-3649 |
| 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-3635 |
| Analytics Builder | Mathematical expressions present in the block documentation for the Discrete Statistics block were not displayed incorrectly in the web application. This issue has now been resolved. | PAB-3439 |
| EPL Apps | Performance optimizations have been made which should improve high-throughput measurement use cases. | PAB-3613 |
| Smart rules | There was a bug in which it was possible for a smart rules creation and update request to complete before the configuration was validated. This issue has now been resolved. | PAB-3663 |
| Smart rules | The smart rule implementation now handles concurrent CRUD requests with the same ID as the smart rule and ensures the consistency of the smart rule instances (that is, no stale smart rules instances are running). | PAB-3656 |
Release 10.14.0.4
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-3325 |
| 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-3365 |
Release 10.14.0.3
In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.14.0.2 release.
Fixes
| Component | Description | Issue |
|---|---|---|
| Streaming Analytics application | The Streaming Analytics application has been updated to use the 10.14.0.133 Web SDK. See also Applications. | PAB-3334 |
Release 10.14.0.2
In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.14.0.1 release.
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | 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-3279 |
| 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-3248 |
Release 10.14.0.1
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-3157 |
| Analytics Builder | Unlike the Models tab in Analytics Builder, the new Samples tab did not show the version information at the bottom of the tab. This has now been fixed. | PAB-3153 |
| Analytics Builder | The Analytics Builder samples have been improved to closely match the behavior of the smart rules. | PAB-3168 |
Release 10.14.0
Apama correlator version
This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.11.3 correlator. EPL apps developers should also refer to What’s New In Apama 10.11.3 in the Apama documentation.
Improvements for monitoring
The following monitoring endpoints are now available for REST requests: /service/cep/health and /service/cep/prometheus.
See Monitoring REST endpoints in the Streaming Analytics guide for detailed information.
Improvements in Analytics Builder
Samples are now provided in the model manager. These are similar to the smart rules in Cumulocity IoT. The samples are intended to help you get started with creating your own models. You can use a sample as a basis for further development by creating a new model from the sample. You can then edit the new model according to your requirements and deploy it. See also First steps: Creating a model from a sample and the description of the new Samples tab in The model manager user interface in the Analytics Builder documentation.
The Measurement Output block now has a new Time input port. This can be used to set the timestamp of the measurement and works similar to the already existing Time input ports of the Alarm Output and Event Output blocks.
The Measurement Input block
now also sends a new property named value as part of its output value. This allows other blocks, such as the
Text Substitution block,
to use the measurement value (for example, to use it in an alarm text).
See also Important announcements regarding the renaming of the Measurement Input block’s frgmentproperty name.
Known issues
The template parameter names in the samples are currently only available in English. It is planned to translate them into the supported languages in a later release.