Databases Reference
In-Depth Information
To specify the recipient of the alert, click on
<Destination>
. This will launch
the
'Select Alert Destination
' window, where we can search for and select any
previously defined destination.
Destinations are created and configured in the Service Bus console. This gives us the
flexibility to change the actual recipient of the alert at a later point in time, just by re-
configuring the destination appropriately.
Enabling alerts
In order for pipeline alerts to be generated, you must first enable them. Otherwise,
Alert actions will just be skipped during the execution of the proxy service. Alerts
need to be enabled in two places, first at the server level and then at the proxy
service level.
To enable them globally, click on the
Operations
tab with the Service Bus console
and then select
Global Settings
. This will display the
Global Settings
window.
From here, ensure the option
Enable Pipeline Alerting
is checked.
Once enabled globally, we can then specify settings for a proxy service. Select the
proxy service, and then click on the
Operational Settings
tab, as shown in the
following screenshot:
Select the checkbox for
Pipeline Alerting
and then from the
Enabling Alerting at
drop-down list select the level of alerting required. This will suppress the generation
of any alerts with a lower severity. So in the preceding example, we have enabled
alerting at the
Warning
level or above, so any alert actions in the proxy service with
a severity level of
Normal
will be skipped.
Handling transient faults
Transient faults typically manifest themselves as non-responsive URIs (that is, no
response is being received for a particular service endpoint), which the Service Bus
indicates with the error code BEA-380002.
