IBM Cloud Docs
Testing destinations

Testing destinations

In today's interconnected digital landscape, maintaining the health and integrity of your connections is paramount. Ensuring your destinations deliver events reliably and connection to the third party apps is always up to date is vital. To ensure that your connection to your destination is correct, you can validate it with a test.

Currently this functionality supports following destinations:

  1. Slack
  2. PagerDuty
  3. ServiceNow
  4. Microsoft® Teams
  5. IBM Cloud Code Engine
  6. IBM Cloud Object Storage

Before you begin

Before you can start testing your destinations, you must have the following prerequisites:

  • A valid destination configuration.
  • Access to the Event Notifications UI or the valid credentials for the API calls.

Testing your destination

  1. Go to the Event Notifications UI.

  2. Click the Destinations tab.

  3. In the row for the destination that you want to test, click the three dots and then select Test. Wait for the test to finish.

  4. Review your results. When the test is completed, you are presented with the results. The results typically include the following information.

    • Status: Whether the test is successful or failed.
    • Response Code: In the event of a test failure, the response code from the end destination client is returned.
    • Response Message: In the event of a test failure, the response message from the end destination client is returned.
    • Destination Activity: If test is successful, you will see a test event delivered onto the desired destination, which will create a new message in case of Slack, Microsoft® Teams, a new incident in case of PagerDuty and ServiceNow, a new invoke in case of IBM Cloud Code Engine, and at last a new object created under a provided bucket in case of IBM Cloud Object Storage.