In the case of using CloudHub 1.0, Custom alerts and notifications are often used in the Non-API application (i.g. Scheduler, MQ listener) for error notification.
Unfortunately, CloudHub 2.0 does not support custom notifications for now.
CloudHub 2.0 for CloudHub 1.0 Users | MuleSoft Documentation
We need to consider alternatives, in using CloudHub 2.0.
Sending an email directly using an Email connector and Amazon SES may be one workaround, but it depends on external service.
And I’d rather not change the architecture from the current.
I believe to be supported some notification function in CloudHub 2.0 near future.
I came up with an interim measure until that is implemented.
It's so simple, using custom notifications on CloudHub 1.0 in CloudHub 2.0.
Create empty application and deploy it to CloudHub 1.0, it called 'customer-papi-alert', and stop it. (save vCores)
And set the alerts on 'customer-papi-alert'.
Create real application and deploy it to CloudHub 2.0, it called 'customer-papi'.
The domain field of 'Create Notification' is 'customer-papi-alert'.
The illustrate for behavior.
That's it.
Top comments (0)