Skip to content

en-destination-event-streams.md

Latest commit

 

History

History
101 lines (59 loc) · 5.69 KB

en-destination-event-streams.md

File metadata and controls

101 lines (59 loc) · 5.69 KB
Raw
copyright
years
2026
lastupdated 2026-02-23
keywords event-notifications, event notifications, about event notifications, destinations, Event Streams, event streams
subcollection event-notifications

{{site.data.keyword.attribute-definition-list}}

{{site.data.keyword.messagehub}}

{: #en-destinations-event-streams}

{{site.data.keyword.messagehub}} is a message bus that is built by using Apache Kafka. It has high throughput and is optimized for event ingestion into {{site.data.keyword.cloud_notm}} and event stream distribution between your services and applications. In Event Streams, applications can send data by creating messages and sending to a topic. To receive messages, the application subscribes to a topic and can choose to receive all the messages of the topic or share the messages between them. {: shortdesc}

{{site.data.keyword.messagehub}} represents a service destination. Since {{site.data.keyword.messagehub}} is a Kafka managed service, incoming notifications cannot be stored and consumed programmatically because Kafka does not store the data once it has been read.

Before you begin

{: #en-event-streams-prerequisites}

Configuring an {{site.data.keyword.messagehub}} destination in the console

{: #en-destinations-event-streams-configure}

If you are using {{site.data.keyword.en_short}} CLI or API to configure an {{site.data.keyword.messagehub}} service instance as a destination, ensure that you have enabled authorization to grant access between services before integrating with {{site.data.keyword.messagehub}}. For more information, see Using authorizations to grant access between services. {: important}

To configure an {{site.data.keyword.messagehub}} destination, complete the following steps:

  1. Navigate to https://cloud.ibm.com , click the Menu icon hamburger icon > Resource List > Developer Tools > Your Event Notifications instance.

  2. From your {{site.data.keyword.en_short}} instance dashboard, click Destinations.

  3. Click Add + to add a new destination.

  4. Provide the name, description (optional) and select the destination type as {{site.data.keyword.messagehub}} and the account where the {{site.data.keyword.messagehub}} instance is located.

    If the {{site.data.keyword.messagehub}} instance is located in the same account as your {{site.data.keyword.en_short}} instance:

    1. Select the name of the {{site.data.keyword.messagehub}} instance to send notifications to.
    2. Once the instance is selected, the Endpoint field will be filled automatically by pulling it from the selected instance.
    3. Select the Topic to send/receive messages from. To select the topic, see Topic.

    If the {{site.data.keyword.messagehub}} instance is located in a different account, provide the following details:

    1. Enter the {{site.data.keyword.messagehub}} CRN . For more information, see CRN.
    2. Enter the {{site.data.keyword.messagehub}} endpoint URL. For more information, see Endpoint url.
    3. Select the topic to send/receive messages from. To select the topic, see Topic.

  5. Click Add.

Finding the {{site.data.keyword.messagehub}} service instance details

{: #en-event-streams-details}

  1. Login to your {{site.data.keyword.cloud_notm}} account.

  2. Navigate to Resource List in the menu.

  3. Navigate to Integration in the Resource list.

  4. Click the {{site.data.keyword.messagehub}} name that displays your {{site.data.keyword.messagehub}} console.

  5. From the {{site.data.keyword.messagehub}} console:

CRN

{: #en-crn}

Copy the CRN, that is used in the destination creation process. Use this copied CRN in the destination creation screen.

Endpoint URL

{: #en-event-streams-endpoint-url}

Copy the HTTP API endpoint that needs to be used in the destination creation process. Use this copied endpoint in the destination creation screen.

Topic

{: #en-topic}

Navigate to Topics in the menu. You will find the list of available topics. Select the topic that you want to send messages to or receive messages from. Copy the Topic Name that needs to be used in the destination creation process. Use this copied name in the destination creation screen.

Creating an authorization in the console

{: #en-using-s2s-console-event-streams}

An authorization is required to grant one service access to another service.You must grant Event Notifications the appropriate IAM service-to-service access so that it can publish messages to Event Streams.

To learn the process to create an authorization between {{site.data.keyword.en_short}} and {{site.data.keyword.messagehub}}, refer Authorization between services.

{{site.data.keyword.messagehub}} retry policy

{: #en-event-streams-retry}

When sending notifications to {{site.data.keyword.messagehub}}, issues such as network errors and application glitches can cause the requests to fail. {{site.data.keyword.en_short}} automatically retries failed requests to provide resiliency.

For detailed information about retry behavior, including retry attempts, delays, and timeout values, see Retry policy for destinations.