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:

  1. Slack
  2. PagerDuty
  3. ServiceNow
  4. Microsoft® Teams
  5. IBM Cloud Code Engine
  6. IBM Cloud Object Storage
  7. Webhook
  8. App Configuration

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

  1. From your Event Notifications instance, click Destinations.

  2. For the destination that you want to test, click the Options menu and select Test. Wait for the test to finish.

  3. When the test is complete, 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, a test event is delivered to the destination. The activity varies by destination type: a new message is created for Slack, Webhook, and Microsoft® Teams; a new incident is created for PagerDuty and ServiceNow; a new invocation occurs for IBM Cloud Code Engine; and a new object is created in the specified bucket for IBM Cloud Object Storage.