Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 127

Usage Statistics App - Allow Calculated Metrics & Thresholds

Overview: To support custom pricing models built on top of Cumulocity IoT, the user needs the ability to define custom metrics using the existing data set. In addition, the user should be able to define thresholds on these custom metrics, so that ...
Tal Dunne 10 months ago in Cumulocity IoT SaaS Enablement 0 Future consideration

User-defined 'Titles' and usage 'Descriptions' for Analytics Builder block instances

Even relatively simple models in Analytics Builder can be tricky to understand. Right now, the only method to document the design intent, or the method of operation of a model is to enter a lengthy description into the "Description" field in the M...
Neil C about 1 year ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Analytics Builder 1 Future consideration

Analytics Builder "Simulation Mode" should support simulating groups of devices

Analytics Builder currently has a simulation mode, which allows an Analytics Builder to consume historical data from the Operational Store (MongoDB), and feed it in real-time to a model. However, this simulation capability is limited to models tha...
Neil C over 1 year ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Analytics Builder 0 Future consideration

Allow customers to use data export functionality without global read access

See support ticket 5398161 for more info. We would like to allow customers to be able to download the measurement data, without requiring the global role that gives them access to everyones data. In particular we'd like them to be able to schedule...
Guest about 4 years ago in Cumulocity IoT DataHub 5 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 5 months ago in Cumulocity IoT Platform Services / Data at Rest 1 Future consideration

Implementation of Wildcard search option at Device credentials page

Currently Device Credentials page is not having any filtering option on the basis of wild search. Also we are not observing sorting option as well. So we are proposing the implementation of the filtering on the basis of wild search(*) and Sorting ...
Akshay Zade 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Future consideration

Implementation of Sorting and Filtering options for Device registration page

Currently Device Registration page has no sorting and filtering options availabl We are proposing the implementation of the below that would enhance the UI experience and also help in troubleshooting for Device Registration page(Device Management=...
Akshay Zade 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 4 Future consideration

Device names from OPCUA server

The device name is generated automatically. It would be helpful if the name could be read from the OPCUA server and used as the device name.
Marius Walzog 6 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1 Future consideration

Allow custom LwM2M decoder microservice to create/update arbitrary inventory fragments

A custom decoder microservice can return dataFragments to the LwM2M agent in order to update the managed object, but this is only capable of updating the fragment specific to the LwM2M resource, e.g. "dataFragments" :[ { "value" : "Hello World" , ...
Guest 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 2 Future consideration

Access timestamp from custom LwM2M decoder microservice

When a decoder microservice is used as a custom action to process a LwM2M payload, it would be useful to have access to the timestamp if it it present in the SenML-JSON/CBOR message. That is, if the payload is received by the LwM2M agent as the re...
Guest 12 months ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Future consideration