Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Cumulocity IoT Platform Services

Showing 127

Retention Rule for Binary Store

We create exports in our application. Now it would be nice to have the possibility to create a retention rule to delete exports older than x-days. ATM that seems not be possible.
Florian Gopp over 2 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Notification2.0 / Puldsar accessiible from external

In Hilti we have several IoT Stack based on different technologies and we need to integrate the ingestion of timeseries data with Cumulocity, we would like to send data from our Kinesis to Pulsar directly (via Cumulocity API) and we would need to ...
Guest 10 months ago in Cumulocity IoT Platform Services 0 Unlikely to support

Support more subtenant levels than two after management tenant.

Tenant user's are enterprises which asks more flexibility in tenant hierarchy. Owner of tenant may want to create subtenants which mimics hierarchy of departments and/or projects. Number of levels can easily go beyond currently available two level...
Guest about 5 years ago in Cumulocity IoT Platform Services / Platform Management 1 Likely to support/improve

Change ACKNOWLEDGED alarm state to ACTIVE and add an audit record when a new alarm is raised but de-duplicated

The Cumulocity API documentation explains the alarm de-duplication behaviour as follows: If an ACTIVE or ACKNOWLEDGED alarm with the same source and type exists, no new alarm is created. Instead, the existing alarm is updated by incrementing the c...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data at Rest / Platform Management 2 Clarification needed

Databroker filtering process

Filtering process is not good enough. It does not allow to filter by different fragments. We need to create 1 filter per fragment. It would be nice to have some sort of "OR" filter for fragments, so we could add as many fragments as needed into 1 ...
Guest almost 2 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Future consideration

Alarm Synchronization DataBroker

Databroker currently synchronizes objects from edge instance to cloud instance based on events occurring in Cumulocity Edge. Same requests sent to Cumulocity Edge are sent to Cloud instance. When losing connection in the Edge side, Databroker is e...
Guest almost 2 years ago in Cumulocity IoT Platform Services / Data in Motion 1 Future consideration

Support for bulk alarm uploads using normal REST

No REST support for uploading bulk alarms. Many of our field devices don't have the capability to communicate with the cloud directly, and hence when it is connected to the docking station, the docking station will download all the data from the f...
Guest 12 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

Option to restart/kill a microservice

In some cases we might want to restart da docker container manually.An option for that could be quite usefull in case someone would need it. Just had an issue with a microservice which showed up as failed, but cumulocity was somehow unable to corr...
Guest about 4 years ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 0 Future consideration

Native IPv6 Support

Simplifies architecture for NTT as no NAT is necessary Nordex wants this for its own microservices NTT gets this as requirement from their customers
Nikolaus Neuerburg over 5 years ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 0 Likely to support/improve

Allow custom properties in SSO as is possible in the user api

Currently you can set some fields through SSO like name email id etc. You can not set custom properties like language preference unit preference. If you do not use SSO you can set custom properties on users.
Tom Michiels about 2 years ago in Cumulocity IoT Platform Services / Authentication & Authorisation 3 Future consideration