Testing destinations
Maintaining the health and integrity of your connections is paramount. Making sure that your destinations deliver events reliably and the connection to the third-party apps is always up to date, is vital. To verify that the connection to your destination is correct, you can run a test.
Currently the following destinations support this functionality:
- Slack
- PagerDuty
- ServiceNow
- Microsoft® Teams
- IBM Cloud Code Engine
- IBM Cloud Object Storage
- Webhook
Before you begin
Before you can start testing your destinations, you must have the following prerequisites in place:
- A valid destination configuration.
- Access to the Event Notifications console or the valid credentials for the API calls.
Testing your destination
-
Go to the Event Notifications console.
-
Click the Destinations tab.
-
For the destination that you want to test, click the overflow menu
and then select Test. Wait for the test to finish.
-
When the test is completed, you are presented with the results. Review your results. The results typically include the following information:
- Status: Whether the test is successful or failed.
- Response Code: If there is a test failure, the response code from the end destination client is returned.
- Response Message: If there is a test failure, the response message from the end destination client is returned.
- Destination Activity: If the test is successful, you see that a test event is delivered to the desired destination, which will create a new message in the case of Slack, Webhook and Microsoft® Teams, a new incident in the case of PagerDuty and ServiceNow, a new invoke in the case of IBM Cloud Code Engine, and a new object is created under a provided bucket in the case of IBM Cloud Object Storage.