Cumulocity IoT Feedback Portal
If the Cumulocity platform is used for a Data as a Service platform used for an integration in a 3rd-party application, we should be able to monitor and manage the consumers using the Notification 2.0 API.
Dead or unused subscriptions seem to block resources that need to be managed in some way via the Administration application.
At least we should have the following information:
List of Subscriptions
List of Subscribers using / used the Subscription
State connected/disconnected
Date/Time of last connect
Account who has created the last token
Summary
State at least one subscriber is connected yes/no
Last connection date/time when subscription was used
Actions
Delete a subscription manually
Retention time until a subscription is automatically deleted after the last subscriber unsubscribes.
Hello Jane,
thank you for the positive feedback. My mail address is frank.bauer@wika.com.
Yesterday I had to unsubscribe more than 500 subscribers. I received a csv file from your operations team with subscriptions and subscribers because your platform resources were blocked. See also the long conversation track in support ticket SI-508360
If this happens again, the operations team will have to provide this kind of .csv files until the notification2 consumers can be managed in a better way and more efficiently.
Best regards,
Frank
Hi Frank,
Thank you for taking the time to raise this idea for the Notification 2.0 API. We intend to address this usablity area, likely to be in the medium term. We will add you to our list of interested customers for the API and keep you informed of progress, if you can let me have your email address that would help enormously.
Regards, Jane Porter