When an incoming request is received, then an HTTP request is perform to an endpoint that will reply with a timeout error. This is just a simple HTTP listener listening on default port. The errors should be also stored in log files and this connector is not a replacement for these. This option is useful when we want to notify about errors that happened during the execution of Mule Apps. Objects are acceptedĪs a result, the following email notification is triggered: The following connector's properties are mandatory to send INFO notifications: Property When an incoming request is received, then the connector is executed, sending a notification via email. The following sample flow will be used to demonstrate this scenario It's advisable not to abuse of these types of notifications. Please take into account that including notifications steps adds some overhead to the final process (less than 2%) and some of this messages can be obtained performing a proper analysis of the logs files. execution results, metrics of a batch/poller process, etc). ![]() This option is useful when we want to notify about certain business events that are not errors, but are important for decisioning (i.e. This explanation assumes that Anypoint Platform username and password were set creating a new configuration and that configuration was associated with the connector, as follows: Next you'll find examples to send INFO or ERROR notifications. The use of the connector during the development phase is very straigthforward: ![]() Here is an example of both alerts configured:Ĭonnector configuration (Mule Application) This value will be inferred based on the values sent. The value on the Contains column will be matched with the values set by the connector for the Type field of the HTML template. To distinguish between both is important to set the "Condition" of the alert to "Custom application notification" and set the proper Priority as follows: Priority It's recommended to configure to different alerts, one Warning/Critical for errors and one Info for info notifications. In order to trigger the notifications (email) we need to configure alerts in the Runtime Manager. Īnypoint Runtime Manager configuration (Alerts) No primary artifact to deploy, deploying attached artifacts instead. maven-deploy-plugin:2.8.2:deploy (default-deploy) custom-notification-extension. The output of this command would be something like:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |