Notification 2.0 - Each API need to have own Subscription Filter
Currently, Notification 2.0 Subscription Filters are not tied to the respective API. It's a common filter for API lists. Ideally, the same service is required to process Events, Alarms but filter conditions are different for each one.
Thank you for taking the time to raise this insight. From our conversations with you and the team we believe this refers to the ability to have multiple tenant-context subscriptions with different filter criteria (APIs, type filters, etc) and for Cumulocity not to treat those as duplicates and reject all but the first one. We believe this is entirely reasonable and will look to prioritize such a feature as soon as we are able. At the moment the team's focus is on the MQTT Service and completing the private preview and taking that capability to general availability. It may, therefore, be a while before we are able to prioritize this request.
Hi Venkat,
Thank you for taking the time to raise this insight. From our conversations with you and the team we believe this refers to the ability to have multiple tenant-context subscriptions with different filter criteria (APIs, type filters, etc) and for Cumulocity not to treat those as duplicates and reject all but the first one. We believe this is entirely reasonable and will look to prioritize such a feature as soon as we are able. At the moment the team's focus is on the MQTT Service and completing the private preview and taking that capability to general availability. It may, therefore, be a while before we are able to prioritize this request.
Regards, Jane.