Release 10.4.6 (GA)

Release 10.4.6.23

Important for customers deploying and operating their own instance of Cumulocity IoT:

An issue has been identified that can lead to excessive RAM usage which finally leads to problems with the Linux OOM-Killer mechanism. Customers deploying and operating their own instance of Cumulocity IoT, are asked to follow the updated instructions on the configuration of memory settings described here:

• Backend installation > Create the Cumulocity environment file > Important configuration items in the Multi-node installation guide.
• Operational procedures > Karaf memory considerations in the Operations guide.

Info: Release 10.4.6.20 has implemented an improvement, which allows to calculate more accurate statistics on resource consumption of microservices. Currently, this can lead to high CPU load when subscriptions of microservices change frequently.

We will improve this in one of the following maintenance releases but release 10.4.6.23 is still affected. We will keep you informed.

As a workaround to limit CPU costs for this calculation we recommend the following configuration change.

On all core nodes, add the following to /etc/cumulocity/cumulocity-core.properties:

  "concurrency.tenant-usage-flush.core-pool-size" => "1"

    "concurrency.tenant-usage-flush.rejected" => "DISCARD"
    "concurrency.tenant-usage-flush.queue-size" => "1000”

The preferred way of doing this is to apply the changes to the Chef server environment configuration.

Fixes

Release 10.4.6.21-10.4.6.22

Info:

Release 10.4.6.20 has implemented an improvement, which allows to calculate more accurate statistics on resource consumption of microservices. Currently, this can lead to high CPU load when subscriptions of microservices change frequently.

We will improve this in one of the following maintenance releases but release 10.4.6.21 and 10.4.6.22 are still affected. We will keep you informed.

As a workaround to limit CPU costs for this calculation we recommend the following configuration change.

On all core nodes, add the following to /etc/cumulocity/cumulocity-core.properties:

  "concurrency.tenant-usage-flush.core-pool-size" => "1"

    "concurrency.tenant-usage-flush.rejected" => "DISCARD"
    "concurrency.tenant-usage-flush.queue-size" => "1000”

The preferred way of doing this is to apply the changes to the Chef server environment configuration.

Improvements

[REST] There is a new parameter available for requests “ ?dateTo={date}&limit={limit}”. It is no longer required to provide “TO” dates as a parameter. [MTM-28815]

[REST] Severity parameter can now be added to alarm API calls. [MTM-29646]

Fixes

Release 10.4.6.20

Info:

Release 10.4.6.20 has implemented an improvement, which allows to calculate more accurate statistics on resource consumption of microservices. Currently, this can lead to high CPU load when subscriptions of microservices change frequently.

We will improve this in one of the following maintenance releases and keep you informed.

As a workaround to limit CPU costs for this calculation we recommend the following configuration change.

On all core nodes, add the following to /etc/cumulocity/cumulocity-core.properties:

  "concurrency.tenant-usage-flush.core-pool-size" => "1"

    "concurrency.tenant-usage-flush.rejected" => "DISCARD"
    "concurrency.tenant-usage-flush.queue-size" => "1000”

The preferred way of doing this is to apply the changes to the Chef server environment configuration.

Release 10.4.6.19

Improvements

[Administration] The Date to field in the Logs tab of own applications has been removed in order to reduce confusion. Instead, starting from the “dateFrom” date, 2000 logs will be shown. [MTM-29296]

[SMTP] For security reasons, the tenant option property “email.password” was changed to “credentials.email.password”. The “email.password” property is still accepted, but its use is deprecated. [MTM-27919]

Fixes

Releases 10.4.6.15 - 10.4.6.18

Improvements

[Administration] Improved error messages when uploading invalid microservices. [MTM-29033]

[Administration] In the Logs tab, It is now possible to jump to the beginning and the end of logs via navigation buttons. For more info, see Administration > Managing applications. [MTM-27530]

[UI] The application switcher now shows all subscribed external applications. [MTM-28921]

[Web SDK] The Web SDK is now released under the Apache 2.0 license. For more information, see the Web SDK guide.[MTM-28584]

Fixes

Release 10.4.6.14

Fixes

Releases 10.4.6.11 - 10.4.6.13

Fixes

Releases 10.4.6.9 - 10.4.6.10

Fixes

Releases 10.4.6.7 - 10.4.6.8

Fixes

Release 10.4.6.6

Improvements

[Administration] Performance improvements when loading the users list. [MTM-25753]

[UI] New Legal notices item has been added to the right drawer menu. The item will redirect the user to the SoftwareAG empower portal.

Fixes

Release 10.4.6.5

Fixes

Releases 10.4.6.0 - 10.4.6.4

Improvements

[Device Management] The smart groups filter is now configurable.

The filters in the Devices > All Devices page can now be configured. Subsequently, created smart groups will contain these filters.

Apama streaming analytics - New code editor and manager

A new developer experience is available when editing and deploying Apama EPL apps.

Whereas Apama EPL apps were previously uploaded using the Administration application, Apama EPL apps are now managed using a new application called Apama-epl.

The new Apama-epl application includes a management page where you can see all your Apama EPL apps. This page makes it easy to see which apps are activated and gives you the ability to provide each app with a meaningful description.

A full in-browser editor is available to develop your Apama EPL apps without having to manage the code in a separate environment.

When you save and activate your EPL app using the editor, then any syntax errors are reported back immediately in the editor, helping you to ensure your application is in good shape.

If you prefer to develop your application outside of Cumulocity (for example, using the feature-rich Software AG Designer desktop tooling), then you can import your apps into the Apama-epl application.

If you have previously uploaded Apama EPL apps using the Applications > Own applications page, then you have to migrate these apps manually. To do so, import the source code of your existing applications into the Apama-epl application.

If you need the original source code, then note that the previously uploaded Apama EPL apps can be found as *.mon files in the files repository.

Behind the scenes, the microservice named apama-small has been replaced by apama-ctrl and the new user interfaces provided by the Apama-epl application.

For further details on Apama streaming analytics, refer to the Streaming analytics guide.

Device Management/Cockpit - New drag & drop functionality

You can now easily re-structure groups and devices per drag & drop functionality in the navigator.

For details, see Device Management > Grouping devices in the User guide.

Sigfox - Migration to API v2

The Sigfox microservice is now using Sigfox API version 2.

Fixes

Releases 10.4.4 - 10.4.5

Improvements

Fixes

Release 10.4.3

Improvements

Fixes

Release 10.4.2

Improvements

Fixes

Release 10.4.1

Fixes