Recently I have been working with a customer running mule as its main integration platform… Mule Management Console (MMC) is known to be a very not very user-friendly interface, with little help you can get. Mule’s documentation is also not the most intuitve one, but nevermind – I need to accept that Mule is the integration platform, that is it!
But we came across a problem, we wanted Mule to send us alerts whenever an application throws an exception. In each integration the exception strategy is to reset the data being processed as well as to log a fatal message. But our goal was that Mule should send us emails (I know..) whenever there is an exception, in the email we wanted the exception to be written inside the emails body…
First of all…
Number 1: Impossible to set an alert definition for each integration
Mule does not provide you with a wildcard allowing you to have one alert definition for all your deployed integration/application. Therefore, what you need to do is to create an alert for all the different integrations/applications that you want to monitor (see picture 1 below).
Number 2: Documentation does not explain how to have trigger an alert on all exceptions being thrown
This one is pretty bad… As you can see in picture 1, there is an Exception type field… There is no help in the user interface what so ever. This one actually kind of pi**** me off, since it is 2016 and UX has evolved and there are basic rules to follow. Finding the actual correct values for this is hard, since the documentation is not very obvious…
To have an alert, that raises for each Exception type (not specifying a certain exception type) you can actually use wildcards in the Exception Type field.
Using the above text “*Exception*”, an alert in the specified server and application will be raised for whatever exception type that is being thrown.