Integrating the Red Hat Hybrid Cloud Console with third-party applications

Procedure

1. Install the Red Hat Insights Application for Splunk:

   1. Log in to Splunk.
   2. On the home page, search for Red Hat Insights in the filter box and select it.
   3. Click Install. When the installation process completes, the message Install successful displays.
   4. On the home page, click the Settings menu (gear icon). The Apps page opens.
   5. Enter Red Hat Insights in the filter box and then click the magnifying glass. The application appears in the search results.
   6. On the home page, click Find more apps under the Apps heading on the left of the screen. The Browse More Apps page opens.
   7. Enter Red Hat Insights in the filter box and then press the Enter key. Red Hat Insights appears in the search results.
   8. Select Red Hat Insights.
   9. Click Install.
   10. Confirm or enter your Splunk username and password and then click Agree and Install. When the installation process completes, the Complete dialog box opens.

2. Set up the Red Hat Insights Application for Splunk:

   1. In the Complete dialog box, click Open the App. The App configuration page opens.

   2. Click Continue to app setup page. The Set up integration with Red Hat Insights page opens. The page includes the HTTP Event Collector (HEC) name and default index fields.

      

   3. Under Create Red Hat Default Index, click Settings > Index.The Indexes page opens in a new tab.
   4. On the Indexes page, click New Index.
   5. Type a name for the index in the Name field (for example, redhatinsights).
   6. Enter values in the Max raw data size and Searchable retention (days) field.
   7. Click Save. The index you created appears in the Indexes list. It is enabled by default.
   8. On the first Splunk screen, on the Set up integration with Red Hat page, type the name for the HEC in the HEC name field (for example, redhatinsights).
   9. Type the name of the index you just created in the Default index field (for example, redhatinsights).
   10. Click Next.
   11. Click Review and then click Submit. The HEC name that you created appears in the HEC Name field.

   12. Click Next to create the HEC URL and HEC Token.

       

3. Configure Splunk integration in Insights:

   1. Click Copy to copy the HEC URL value in Splunk Enterprise.

   2. Click Next: Configure Splunk integration in Insights. The Hybrid Cloud Console opens in a new browser tab.

      Note

      This button is disabled until you click the Copy button for either the HEC URL or HEC token.

   3. In the Hybrid Cloud Console, navigate to Settings > Integrations.

1. Paste the HEC URL value into the Splunk HEC URL field.

   Note

   If the new tab for the console does not open, disable the popup blocker in your browser.

2. Add the port, if needed. The default port for Splunk Cloud Platform is 443. The default port for Splunk Enterprise and Splunk Cloud free trial is 8088.

   

3. Optional: If you are using Splunk Cloud, edit the HEC URL that you pasted into the Splunk HEC URL field on the Integrations page to match the Splunk Cloud format:

   • Use the following format for Splunk Cloud Platform on all clouds except Google Cloud Platform (GCP):

     <protocol>://http-inputs-<host>.splunkcloud.com:<port>/<endpoint>

   • Use the following format for Splunk Cloud Platform on Google Cloud Platform (GCP):

     <protocol>://http-inputs.<host>.splunkcloud.com:<port>/<endpoint>

     Replace the following placeholders:

   • protocol: Either http or https.
   • host: The name of the Splunk Cloud Platform instance that runs the HEC, followed by the domain .splunkcloud.com.
   • port: The HEC port number (443 by default on Splunk Cloud Platform instances).

   • endpoint: The HEC endpoint that you want to use. In many cases, you use the /services/collector/event endpoint for JSON-formatted events, or the services/collector/raw endpoint for raw events.

     Examples:

   • Splunk Cloud Platform on GCP using JSON:

     https://http-inputs.myhost.splunkcloud.com:443/services/collector/event

   • Splunk Cloud free trial on AWS using raw events:

     https://http-inputs-otherhost.splunkcloud.com:443/services/collector/raw

     1. Complete the setup process:
4. Copy the HEC Token value in Splunk and paste it into the Splunk HEC Token field in on the Hybrid Cloud Console Integrations page.

5. In the Hybrid Cloud Console, click Run configuration. The Hybrid Cloud Console sets up the integration, creates the behavior group, and associates Hybrid Cloud Console events to the behavior group. The status message section on the right side of the page shows the status of each of these actions.

   

6. When the setup completes successfully, click Next: Review. The application returns the message Splunk integration in Insights completed.

   

7. Click Go back to the Splunk application. This redirects you to the Set up integration with Red Hat screen in Splunk.

8. Click Finish set up to complete the setup in Splunk.

   

9. Click Go to dashboard to be redirected to your Splunk dashboard.

   

   Note

   If the integration configuration fails during the Insights setup process, contact Red Hat support.

   1. To view a list of Hybrid Cloud Console events on the Splunk dashboard, click the Events tab. Each event is hyperlinked to the Hybrid Cloud Console.

      

Procedure

1. From the Splunk home page, navigate to Settings.

2. Select Data Inputs, and then select HTTP Event Collector. The HTTP Event Collector page shows the HEC, its Token value, the corresponding index that you selected during setup, and the status of the HEC.

   

3. Click Global Settings in the upper right corner of the page. The Edit Global Settings dialog box displays.

   

4. Select Enabled. This enables the HEC token that was automatically created during the setup process.

   Note

   The HEC token uses a default HTTP port number of 8088. If you are using a different port (such as port 443 for Splunk Cloud), you must update your Hybrid Cloud Console Splunk Integration to match.

Procedure

1. Click Settings > Identity & Access Management.
2. Under Identity & Access Management, expand User Access if necessary, and select Groups.
3. Click Create group. The Name and description page appears.
4. Enter a name for the group (for example, splunknotifgroup), enter a description, and click Next. The Add roles page opens.
5. To add the Notifications administrator role, enter notif in the search box.
6. Select Notifications administrator from the search results list, and click Next. The Add Members page opens.
7. Select the users to add to this group. You can use the search box to search for specific names.
8. Click Next. The Review Details page opens.
9. Review the information, and click Submit to create the group.
10. Click Exit. The Groups page opens.

Verification

1. Enter the new group name in the search box.
2. Click the group name. The page for the group opens.
3. On the Roles tab, verify that the group has the Notifications administrator role.
4. Click the Members tab and verify that the group includes the correct members.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Integrations.
2. Select the Reporting & Automation tab.
3. Click Add integration.
4. Select Splunk as the integration type, and click Next.
5. Enter a name for your new integration in the Integration name field (for example, redhat_splunk).

6. In the Endpoint URL field, add your Splunk HEC endpoint URL:

   1. For Splunk Enterprise, Splunk uses port 8088 by default. For example: https://<splunk-endpoint>:8088

   2. For Splunk Cloud, Splunk uses port 443. For more information about Splunk Cloud on AWS or GCP, see Send data to HTTP Event Collector.

      Note

      The service automatically adds <endpoint> (the http path). You do not need to include it in the form input for the Endpoint URL.

      The following examples show endpoint URLs with the correct port numbers for Splunk platforms.

      • On premise (Splunk Enterprise): https://splunk.company.com:8088
      • Splunk Cloud (on AWS): https://http-inputs-mycompany.splunkcloud.com:443
      • Splunk Cloud (on GCP): https://http-inputs.mycompany.splunkcloud.com:443
7. In the Secret token field, add the Splunk HEC token value.
8. Click Next.
9. Review the integration details and click Submit.

Procedure

1. Log in to your ServiceNow instance.

2. Navigate to the ServiceNow Store home page and install or update the Flow Templates:

   • Install the Flow Templates for Red Hat Insights application from the ServiceNow Store (or as an Update Set).

     1. Create a new user with User ID rh_insights_integration.
     2. Check Internal Integration User for the user you just created.
     3. Ensure that the user is Active.
     4. Assign role x_rhtpp_rh_webhook.rest to the user.
     5. Generate a password for the user. Copy this information for use during the setup process.
3. Open the Hybrid Cloud Console in a new browser window or tab.

4. Navigate to Settings > Integrations, select the Reporting & Automation tab, and complete the following steps:

   1. Click Add integration.
   2. Select ServiceNow as the integration type, and click Next.
   3. Enter a name for the integration, such as ServiceNow integration.

   4. Provide the Endpoint URL and replace <instance.servicenow.com> with your ServiceNow instance:

      https://<instance.servicenow.com>/api/x_rhtpp_rh_webhook/flow_templates_for_red_hat_insights

   5. The checkbox to Enable SSL is checked by default.
   6. In the Secret token field, paste the generated password of the rh_insights_integration user that you created in ServiceNow.
   7. Click Next.
   8. Review the integration details and click Submit.

5. Navigate to Hybrid Cloud Console > Settings > Notifications and complete the following steps:

   1. Under Notifications, select Configure Events.
   2. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
   3. Click the Behavior Groups tab.
   4. Click Create new group to open the Create behavior group wizard.
   5. Type the name of the new behavior group in the Name field and click Next.
   6. For Actions, select Integration: ServiceNow from the drop-down list.
   7. For Recipient, select the integration for ServiceNow that you created earlier (for example, ServiceNow integration).
6. Click Next. The Associate event types window opens.

7. Select the following event types from the list:

   • Advisor new recommendation
   • New vulnerability with CVSS >= 7.0
   • New vulnerability with Critical Severity
   • New vulnerability containing Security rule
   • Any vulnerability with known exploit
8. Click Next, and then click Finish to complete the setup process.

Procedure

1. Create a Slack app:

   1. Go to the Slack API web page and click the Create your Slack app button. This opens the Create an app dialog.
   2. Select From scratch to use the Slack configuration UI to create your app.

   3. Enter a name for your app and select the workspace where you want to receive notifications.

      Note

      If you see a message that administrator approval is required, you can request approval in the next step.

   4. Click Create App to finish creating the Slack app.

2. Enable incoming webhooks:

   1. Under the Features heading in the left navigation, click Incoming Webhooks.
   2. Toggle the Activate Incoming Webhooks switch to On.
   3. Click the Request to Add New Webhook button. If required, enter a message to your administrators to grant access to your app and click Submit Request. A success message confirms you have configured this correctly.

3. Create an incoming webhook:

   1. Under Settings in the left navigation, click Basic Information.
   2. In the Install your app section, click the Install to Workspace button.
   3. Select the channel where you want your Slack app to post notifications, or select a user to send notifications to as direct messages.
   4. Click Allow to save changes.

4. Optional: Configure how your Hybrid Cloud Console notifications appear in Slack:

   1. Scroll down to Display Information.
   2. Configure your app description, icon, and background color as desired.

5. Copy the webhook URL:

   1. Under Features, click Incoming Webhooks.
   2. Click the Copy button next to the webhook URL. You will use the URL to set up the integration in the Hybrid Cloud Console in Section 3.2, “Configuring the Slack integration in the Red Hat Hybrid Cloud Console”.

Procedure

1. If necessary, go to the Slack API web page and copy the webhook URL that you configured.

   Note

   See Section 3.1, “Configuring incoming webhooks in Slack” for the steps to create a Slack webhook URL.

2. In the Hybrid Cloud Console, navigate to Settings > Integrations.
3. Select the Communications tab.
4. Click Add integration.
5. Select Slack as the integration type and click Next.
6. Enter a name for the integration (for example, My Slack notifications).
7. Paste the Slack webhook URL that you copied from Slack into the Workspace URL field and click Next.
8. To enable the integration, review the integration details and click Submit.
9. Refresh the integrations page to show the Slack integration in the Integrations > Communications list. Under Last connection attempt, the status is Ready to show the connection can accept notifications from the Hybrid Cloud Console.

1. Next to your Slack integration on the Integrations > Communications page, click the options icon (⋮) and click Test.
2. In the Integration Test screen, enter a message and click Send. If you leave the field empty, the Hybrid Cloud Console sends a default message.
3. Open the Slack channel you configured and check for the message sent from the Hybrid Cloud Console.
4. In the Hybrid Cloud Console, go to Notifications > Event Log and check that the Integration: Slack event is listed with a green label.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Notifications.
2. Under Notifications, select Configure Events.
3. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
4. Click the Behavior Groups tab.
5. Click Create new group to open the Create behavior group wizard.
6. Enter a name for the behavior group and click Next.
7. In the Actions and Recipients step, select Integration: Slack from the Actions drop-down list.

8. From the Recipient drop-down list, select the name of the integration you created (for example, My Slack notifications) and click Next.

   

9. In the Associate event types step, select one or more events for which you want to send notifications (for example, Policies: Policy triggered) and click Next.

10. Review your behavior group settings and click Finish. The new behavior group appears on the Notifications > Configure Events page in the Behavior Groups tab.

    Note

    You can create and edit multiple behavior groups to include any additional platforms that the notifications service supports.

11. Select Settings > Integrations and click the Communications tab. When the Slack integration is ready to send events to Slack, the Last connection attempt column shows Ready. If the notification reached Slack successfully, the Last connection attempt column shows Success.

    

Verification

1. Create an event that will trigger a Hybrid Cloud Console notification. For example, run insights-client on a system that will trigger a policy event.
2. Wait a few minutes, and then navigate to Slack.
3. In your Slack channel, check for notifications from the Hybrid Cloud Console.

4. In the Hybrid Cloud Console, go to Settings > Notifications > Event Log and check for an event that shows the label Integration: Slack.

   • If the label is green, the notification succeeded.
   • If the label is red, the integration might need to be adjusted.

5. If the integration is not working as expected, verify that the incoming webhook connector was properly created in Slack, and that the correct incoming webhook URL is added in the Hybrid Cloud Console integration configuration.

   Note

   See Troubleshooting notification failures with the event log and integration settings in the notifications documentation for more details.

Procedure

1. Connect your environment to the Red Hat Ansible Automation Hub:

   1. In the Hybrid Cloud Console, navigate to Ansible Automation Platform > Connect to Hub.
   2. Under Offline token, copy the string under The token will expire after 30 days of inactivity. Run the command below periodically to prevent your token from expiring.
   3. In a terminal window, paste the string that you copied in the previous step.

2. Enter the following command to install the Red Hat Insights collection for Event-Driven Ansible:

   $ ansible-galaxy collection install redhat.insights_eda

3. To install the Red Hat Insights requirements, enter the following command as the root user:

   # pip3 install -r ~/.ansible/collections/ansible_collections/redhat/insights_eda/requirements.txt

4. Enter the following command and verify that redhat.insights_eda is included in the output:

   $ ansible-galaxy collection list

   Sample output for this command:

   # /home/username/.ansible/collections/ansible_collections
   Collection         Version
   ------------------ -------
   ansible.eda        1.3.8
   community.general  7.0.1
   redhat.insights_eda 1.0.0

5. Use a text editor to create a YAML file that contains a simple Ansible rulebook that uses the Red Hat Insights collection. For example, create a file called simple-rulebook.yaml with the following content:

   ---
   - name: Listen for events from Red Hat Insights
     hosts: all
     sources:
       - redhat.insights_eda.insights:
     rules:
       - name: Handle Red Hat Insights payload
         condition: event.payload is defined
         action:
           debug:
             msg: "Received: {{ event.payload }}"

   This simple playbook uses the redhat.insights_eda.insights collection as the source. If an event with payload is defined, the contents of event.payload are displayed as output.

   The rulebook exposes an endpoint that is used to receive events and communicate with the Hybrid Cloud Console. See the Event-Driven Ansible for Red Hat Insights documentation in Ansible Automation Hub for more advanced examples for the Red Hat Insights Advisor, Compliance, and Vulnerability services.

6. Create a YAML file that contains an associated playbook. For example, create a file called inventory.yaml that contains a simple inventory:

   all:

7. Run the ansible-rulebook command to start your Event-Driven Ansible listener to listen for new events. In the following example, this command exposes your localhost on the default port 5000:

   $ ansible-rulebook --verbose --rulebook simple-rulebook.yml -i inventory.yml

8. Run the curl command in a separate terminal window to verify that your Event-Driven Ansible listener is configured correctly, for example:

   $ curl -H 'Content-Type: application/json' -d "{\"payload\": \"Test incoming event\"}" localhost:5000/endpoint

   In this example, if the configuration is correct, a new message appears in the EDA listener window with the content of the event:

   Received: {'payload': 'Test incoming event'}

9. In the Hybrid Cloud Console, navigate to Settings > Integrations.
10. Select the Reporting & Automation tab.
11. Click Add integration.
12. Select Event-Driven Ansible as the integration type, and then click Next.
13. In the Integration name field, enter a name for your integration (for example, My EDA Integration).

14. Enter the URL that you configured in your Ansible rulebook into the Endpoint URL field. This is the endpoint that points to the Event-Driven Ansible listener.

    Note

    The Endpoint URL must include http:// or https://, for example https://<eda_hostname>:5000/endpoint.

    If necessary, ask the security administrator for your organization to configure access to the Red Hat Hybrid Cloud Console.

15. Optional: Enter a Secret token if one is configured.

    Note

    A secret token is essential for protecting the data sent to the integration endpoint and should always be used when integrating the Hybrid Cloud Console with third-party applications.

16. Click Next.
17. Review the integration details, and then click Submit to enable the integration.

1. Next to your Event-Driven Ansible integration on the Integrations > Reporting & Automation page, click the options icon (⋮) and click Test.
2. In the Integration Test screen, enter a message and click Send. If you leave the field empty, the Hybrid Cloud Console sends a default message.
3. In the Event-Driven Ansible listener terminal, check for the message sent from the Hybrid Cloud Console.
4. In the Hybrid Cloud Console, go to Notifications > Event Log and check that the Integration: Event-Driven Ansible event is listed with a green label.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Notifications.
2. Under Notifications, select Configure Events.
3. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
4. Click the Behavior Groups tab.
5. Click Create new group to open the Create behavior group wizard.
6. Type a name for the behavior group and click Next.
7. In the Actions and Recipients step, select Integration: Event-Driven Ansible from the Actions drop-down list.
8. From the Recipient drop-down list, select the name of the integration you created (for example, My EDA Listener) and click Next.
9. In the Associate event types step, select one or more events for which you want to send notifications (for example, Advisor: New recommendation) and click Next.
10. Review your behavior group settings and click Finish. The new behavior group appears on the Notifications page.

Verification

1. Create an event that will trigger a Hybrid Cloud Console notification. See the Ansible Automation Hub page for an example.

2. To test that the Hybrid Cloud Console integration was successful, in the Hybrid Cloud Console, go to Settings > Notifications > Event Log and check for an event that shows the label Integration: Event-Driven Ansible.

   

   • If the label is green, the notification succeeded.
   • If the label is red, verify that the webhook has been properly created and exposed in Event-Driven Ansible, and that the correct webhook URL is configured in the Hybrid Cloud Console integration configuration.

Procedure

1. Create a new channel in Microsoft Teams or select an existing channel.
2. Navigate to Apps and search for the Incoming Webhook application.
3. Select the Incoming Webhook application and click Add to a team.
4. Select the team or channel name and click Set up a connector.
5. Enter a name for the incoming webhook (for example, Red Hat Notifications). This name appears on all notifications that the Microsoft Teams channel receives from the Red Hat Hybrid Cloud Console through this incoming webhook.
6. Optional: Upload an image to associate with the name of the incoming webhook. This image appears on all notifications that the Microsoft Teams channel receives from the Hybrid Cloud Console through this incoming webhook.
7. Click Create to complete creation and display the webhook URL.
8. Copy the URL to your clipboard. You need the URL to configure notifications in the Hybrid Cloud Console.
9. Click Done. The Microsoft Teams page displays the channel and the incoming webhook.
10. In the Hybrid Cloud Console, navigate to Settings > Integrations.
11. Click the Communications tab.
12. Click Add integration.
13. Select Microsoft Office Teams as the integration type, and click Next.
14. In the Integration name field, enter a name for your integration (for example, console-teams).
15. Paste the incoming webhook URL that you copied from Microsoft Teams into the Endpoint URL field.
16. Click Next.
17. Review the integration details and click Submit to enable the integration.

1. Next to your Microsoft Teams integration on the Integrations > Communications page, click the options icon (⋮) and click Test.
2. In the Integration Test screen, enter a message and click Send. If you leave the field empty, the Hybrid Cloud Console sends a default message.
3. Open your Microsoft Teams channel and check for the message sent from the Hybrid Cloud Console.
4. In the Hybrid Cloud Console, go to Notifications > Event Log and check that the Integration: Microsoft Teams event is listed with a green label.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Notifications.
2. Under Notifications, select Configure Events.
3. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
4. Click the Behavior Groups tab.
5. Click Create new group to open the Create behavior group wizard.
6. Type a name for the behavior group and click Next.
7. In the Actions and Recipients step, select Integration: Microsoft Teams from the Actions drop-down list.
8. From the Recipient drop-down list, select the name of the integration you created (for example, console-teams) and click Next.
9. In the Associate event types step, select one or more events for which you want to send notifications (for example, Policies: Policy triggered) and click Next.
10. Review your behavior group settings and click Finish. The new behavior group appears on the Notifications > Configure Events page in the Behavior Groups tab.

Verification

1. Create an event that will trigger a Hybrid Cloud Console notification. For example, run insights-client on a system that will trigger a policy event.
2. Wait a few minutes, and then navigate to Microsoft Teams.
3. Select the channel that you configured from the left menu. If the setup process succeeded, the page displays a notification from the Hybrid Cloud Console. The notification contains the name of the host that triggered the event and a link to that host, as well as the number of events and a link that opens the corresponding Hybrid Cloud Console service.

4. In the Hybrid Cloud Console, go to Settings > Notifications > Event Log and check for an event that shows the label Integration: Microsoft Teams.

   • If the label is green, the notification succeeded.

   • If the label is red, verify that the incoming webhook connector was properly created in Microsoft Teams, and that the correct incoming webhook URL is added in the Hybrid Cloud Console integration configuration.

     Note

     See Troubleshooting notification failures with the event log and integration settings in the notifications documentation for more details.

Procedure

1. In your Google space, click the arrow on the space name to open the dropdown menu:

   1. Select Apps & Integrations.
   2. Click Webhooks.

2. Enter the following information in the Incoming webhooks dialog:

   1. Enter a name for the integration (for example, Engineering Google Chat).
   2. Optional: To add an avatar for the notifications, enter a URL to an image.
   3. Click Save to generate the webhook URL.
   4. Copy the webhook URL to use for configuration in the Hybrid Cloud Console.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Integrations.
2. Select the Communications tab.
3. Click Add integration.
4. Select Google Chat as the integration type, and click Next.
5. In the Integration name field, enter a name for your integration (for example, console-gchat).
6. Paste the incoming webhook URL that you copied from your Google space into the Endpoint URL field, and click Next.
7. Review the integration details and click Submit to enable the integration.

1. Next to your Google Chat integration on the Integrations > Communications page, click the options icon (⋮) and click Test.
2. In the Integration Test screen, enter a message and click Send. If you leave the field empty, the Hybrid Cloud Console sends a default message.
3. Open your Google space and check for the message sent from the Hybrid Cloud Console.
4. In the Hybrid Cloud Console, go to Notifications > Event Log and check that the Integration: Google Chat event is listed with a green label.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Notifications.
2. Under Notifications, select Configure Events.
3. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
4. Click the Behavior Groups tab.
5. Click Create new group to open the Create behavior group wizard.
6. Type a name for the behavior group and click Next.
7. In the Actions and Recipients step, select Integration: Google Chat from the Actions drop-down list.
8. From the Recipient drop-down list, select the name of the integration you created (for example, console-gchat) and click Next.
9. In the Associate event types step, select one or more events for which you want to send notifications (for example, Policies: Policy triggered) and click Next.
10. Review your behavior group settings and click Finish. The new behavior group is listed on the Notifications page.

Verification

1. Create an event that will trigger a Hybrid Cloud Console notification. For example, run insights-client on a system that will trigger a policy event.
2. Wait a few minutes, and then navigate to Google Chat.
3. In your Google Space, check for notifications from the Hybrid Cloud Console.

4. In the Hybrid Cloud Console, go to Settings > Notifications > Event Log and check for an event that shows the label Integration: Google Chat.

   • If the label is green, the notification succeeded.
   • If the label is red, the integration might need to be adjusted.
5. If the integration is not working as expected, verify that the incoming webhook connector was properly created in Google Chat, and that the correct incoming webhook URL is added in the Hybrid Cloud Console integration configuration.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Integrations.
2. Click the Webhooks tab.
3. Click Add integration.
4. In the Integration name field, enter a name for your integration.
5. Paste the webhook URL from your third-party application into the Endpoint URL field.

6. Optional: Enter a Secret token if one is configured.

   Note

   A secret token is essential for protecting the data sent to the integration endpoint and should always be used when integrating the Hybrid Cloud Console with third-party applications.

7. Click Next.
8. Review the integration details and click Submit to enable the integration.
9. Refresh the integrations page to show the webhook integration in the Integrations > Webhooks list. Under Last connection attempt, the status is Ready to show the connection can accept notifications from the Hybrid Cloud Console.

1. Next to your integration on the Integrations > Webhooks page, click the options icon (⋮) and then click Test.
2. In the Integration Test screen, enter a message and click Send. If you leave the field empty, the Hybrid Cloud Console sends a default message.
3. Open your third-party application and check for the message sent from the Hybrid Cloud Console.
4. In the Hybrid Cloud Console, go to Notifications > Event Log and check that the Integration: Webhook event is listed with a green label.

Procedure

1. In the Hybrid Cloud Console, navigate to Settings > Notifications.
2. Under Notifications, select Configure Events.
3. Select the application bundle tab you want to configure event notification behavior for: Red Hat Enterprise Linux, Console, or OpenShift.
4. Click the Behavior Groups tab.
5. Click Create new group to open the Create behavior group wizard.
6. Type a name for the behavior group and click Next.
7. In the Actions and Recipients step, select Integration: Webhook from the Actions drop-down list.
8. From the Recipient drop-down list, select the name of the webhook integration you created and click Next.
9. In the Associate event types step, select one or more events for which you want to send notifications (for example, Policies: Policy triggered) and click Next.
10. Review your behavior group settings and click Finish. The new behavior group appears on the Notifications > Configure Events page in the Behavior Groups tab.

Verification

1. Create an event that will trigger a Hybrid Cloud Console notification. For example, run insights-client on a system that will trigger a policy event.
2. Wait a few minutes, and then navigate to your third-party application to check for a notification.

3. In the Hybrid Cloud Console, go to Settings > Notifications > Event Log and check for an event that shows the label Integration: Webhook.

   • If the label is green, the notification succeeded.

   • If the label is red, verify that the incoming webhook connector was properly created in your application, and that the correct incoming webhook URL is added in the Hybrid Cloud Console integration configuration.

     Note

     See Troubleshooting notification failures with the event log and integration settings in the notifications documentation for more details.