Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

Data at Rest

Showing 14 of 387

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

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 over 4 years ago in Cumulocity IoT Platform Services / Data at Rest 3 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 about 2 years ago in Cumulocity IoT Platform Services / Data at Rest 0 Future consideration

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

moving up from child MO to parent MO in the hierarchy issue

Kemin encountered this situation: a Device has a child device assigned. An user has inventory read access on a device group, both devices are assigned to this device group. For Kemins use case, they need to find the ID of the parent device based o...
Guest about 1 month ago in Cumulocity IoT Platform Services / Data at Rest 1 Planning / planned

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

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

Case insensitive queries on API

Do queries on managed objects with third party integrated data, which does not always underlie a defined semantic. For instance do a query for all devices having a specific property value of abc or Abc or ABC etc.
Guest almost 5 years ago in Cumulocity IoT Platform Services / Data at Rest 2 Unlikely to support

Apama-like script engine for reading data from database

Sometimes it would be helpful to have a real time engine for outgoing data, like Apama for incoming data. We could change values of measurements to other units or filter data before they get send to the client. Maybe we can use it for calculating ...
Helmut Gansmüller 5 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Clarification needed