Release 10.16.0.7
In this release, the Apama-ctrl microservice uses the same Apama version as in the previous 10.16.0.6 release.
Fixes
| Component | Description | Issue |
|---|---|---|
| Analytics Builder | The runtime performance of Analytics Builder has been improved when large objects are ingested. | PAB-4430 |
Release 10.16.0.6
This release upgrades the Apama-ctrl microservice to use Apama 10.15.4.1 (which is the same as Apama 10.15 Fix 17).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | For reasons of security and performance, the REST endpoint /service/cep/health no longer returns a comprehensive list of status values. All of the same information is still available from REST endpoints under /service/cep/diagnostics/.... |
PAB-4361 |
| Analytics Builder | Asynchronous alarm inputs declared by the Alarm Output blocks were considered for connectivity chains between models, leading to "Internal error : inconsistent chain ID" errors in some scenarios. This has been fixed now. | PAB-4395 |
Release 10.16.0.5
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
| Component | Description | Issue |
|---|---|---|
| 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-4108 |
Release 10.16.0.4
This release upgrades the Apama-ctrl microservice to use Apama 10.15.3.0 (which is the same as Apama 10.15 Fix 11).
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-3691 |
| 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-4025 |
| Analytics Builder and EPL Apps | The icons are now shown properly when the Streaming Analytics application is shown in the Japanese and Chinese languages. | PAB-3953 |
Release 10.16.0.3
This release upgrades the Apama-ctrl microservice to use Apama 10.15.2.3 (which is the same as Apama 10.15 Fix 9).
Fixes
| Component | Description | Issue |
|---|---|---|
| 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-3666 |
| Apama runtime | Starting with release 10.16, the Cumulocity IoT platform performs more strict validations on incoming fields of email requests.
When the bcc field of the com.apama.cumulocity.SendEmail event was empty,
the Apama HTTP client transport for Cumulocity IoT incorrectly forwarded the bcc field as an empty string
instead of as a JSON array, causing requests to be rejected. This issue has now been resolved. |
PAM-34264 |
Release 10.16.0.2
This release upgrades the Apama-ctrl microservice to use Apama 10.15.2.1 (which is the same as Apama 10.15 Fix 7).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | The /prometheus endpoint of the Apama-ctrl microservices is now
restricted to only the bootstrap tenant and internal monitoring from Cumulocity IoT operations.
It now contains all of the metrics published by the correlator and user applications running in it.
|
PAB-3606 |
| 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-3655 |
| 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-3651 |
| 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-3637 |
| EPL Apps | Performance optimizations have been made which should improve high-throughput measurement use cases. | PAB-3615 |
| 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-3658 |
Release 10.16.0.1
This release upgrades the Apama-ctrl microservice to use Apama 10.15 Fix 3 (which is the same as Apama 10.15.1.0).
Fixes
This release does not contain any fixes.
Release 10.16.0
Apama correlator version
This release of Cumulocity IoT Streaming Analytics includes the Apama version 10.15.1 correlator. EPL apps developers should also refer to What’s New In Apama 10.15.1 in the Apama documentation.
Improvements in Analytics Builder
The Type parameter of the Selector block now supports JSON for setting the type of the output value. If JSON is selected as the type, all input parameter values must be valid JSON values of the same type. This allows the Selector block to output properties which can be used, for example, with the Set Properties block to generate different sets of properties for the output blocks, depending on which input port of the Selector block is enabled.
The Combiner block now offers a new mode called Latest Updated. When selected, it outputs the value which was most recently updated, even if the actual value is not changed. This is useful when you need the latest published value from multiple values. For example, if you have a number of sensors that measure the temperature periodically at different intervals and you want to get the latest temperature received by the block by all of those sensors, you can use the Combiner block with the Latest Updated mode. This provides the latest published temperature, even if a sensor measures and publishes the same temperature. For clarity, the existing Latest mode has been renamed to Latest Changed. When using the Latest Changed mode, a value is not considered changed if the actual value does not change. For example, when using the Latest Changed mode with temperature sensors, it outputs the sensor value whose temperature was most recently changed.
Fixes
| Component | Description | Issue |
|---|---|---|
| Analytics Builder | The reset behavior of the Discrete Statistics block has been corrected. Previously, the block had incorrectly sampled the previous value when resetting, which could result in incorrect statistics. For example, when the Discrete Statistics block was used for counting, the count started with 1 instead of 0 after the reset. This has been fixed so that the block does not sample the previous value after the reset until a new value is received. If a new value is received along with the reset signal, the new value is sampled after the block has been reset. | PAB-3195 | Analytics Builder | The value of the timestamp field of the apama.analyticsbuilder.Value event when used as an input value in a custom block was incorrect in some situations.
This has been fixed so that the timestamp field now contains the correct timestamp of the value.
|
PAB-3363 |