Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Data at Rest

Showing 12 of 369

add a field "received_time" in measurements

I have a use case with logical devices that send batches of measurements. It happens that the data is completed or recomputed at ground side and measurements are sent again to Cumulocity. We experience problems when deleting existing measurements ...
Guest 10 months ago in Cumulocity IoT Platform Services / Data at Rest 2 Future consideration

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same ty...
Peter Gaspar over 2 years ago in Cumulocity IoT Platform Services / Data at Rest 4 Planning / planned

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 4 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

Log User deleting folders by drag and drop

User can drag and drop folders, included sub folders, around all hierarchy. if they do it in the main folder, they will not see that group anymore. you need to log who is doing this kind of actions to solve arising issue.
Guest almost 2 years ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

case-insensitive filtering in inventory

today, the devices from inventory can only be filtered by case sensitive queries for name or other fragment. Idea is to implement option to filter case-insensitevly. MongoDB provides enough expressions to be used to extend filtering options and st...
Peter Gaspar about 4 years ago in Cumulocity IoT Platform Services / Data at Rest 3 Future consideration

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 about 1 year ago in Cumulocity IoT Platform Services / Data at Rest / Platform Management 2 Clarification needed

Recycle bin feature

Currently recycle bin feature is not supported for any of the following items, if deleted: Device protocol – we learned from raimondi that it may stop the transmission of all devices with it Device – customer may delete a device by mistake, after ...
oana velicu 7 months ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

Measurement query for specific group of devices

In the API for Measurement there is no possibility to query for Group Devices. If I have same Device Types with the same Measurement Structure (Type,Fragment,Series) there is no easy way to delete measurements for a group of Devices. It is only po...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

Audit changes for retention in audit log

Users can add retention rules within the Administration application, e.g. add new retention rule that all tenant measurements older than 3 days shall be deleted. This action is not part of the Audit Log. We should audit the changes of retention as...
Guest 11 months ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

Deduplication of alarms doesn't consider severity

If an alarm has the same type and the same source deduplication puts this alarm count. However, if the alarm with same type and source has another severity it is also put to the same group. It can happen that the customer has an alarm with same ty...
Guest over 3 years ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration