Appendix A. Troubleshooting Hybrid Cloud Console integrations
If you experience issues while integrating a third-party application with the Hybrid Cloud Console, review the following troubleshooting solutions.
Notifications for Red Hat Lightspeed services are triggered based on service-specific criteria. For more details about Red Hat Lightspeed events, see Understanding Red Hat Insights Events and Notifications in the Hybrid Cloud Console.
A.1. Troubleshooting connection issues between third-party integrations and Red Hat Lightspeed Copy linkLink copied to clipboard!
If you experience connection issues between your third-party application and Red Hat Lightspeed, ensure that your third-party application accepts incoming requests from the following Red Hat IP addresses:
-
23.20.194.86 -
23.22.242.238 -
54.147.218.140
For the most up-to-date list of IP addresses, see Firewall Configuration for accessing Red Hat Insights / Hybrid Cloud Console Integrations & Notifications.
A.2. Troubleshooting Hybrid Cloud Console integration with Splunk Copy linkLink copied to clipboard!
Review the following issues if your Hybrid Cloud Console console integration with Splunk is not working as expected:
A.2.1. Splunk does not receive event notifications from the Hybrid Cloud Console Copy linkLink copied to clipboard!
Configuration errors in the Splunk environment can result in Splunk not receiving event notifications from the Hybrid Cloud Console.
- In Splunk, make sure that the HTTP Event Collector (HEC) is enabled under Global Settings. See Enabling the HEC token.
-
Make sure that the default index is
redhatinsights. - Make sure the firewall allows for incoming requests on the configured Splunk HEC port (default for Splunk Enterprise is 8088, and default for Splunk Cloud is 443). If you are using AWS for your instance, allow any of the ports Splunk might need. For more information, refer to Splunk Phantom ports and endpoints.
For more information about configuring Splunk HEC ports, see Splunk Phantom ports and endpoints.
A.2.2. Cannot click links in the Events table in Splunk when using real-time search Copy linkLink copied to clipboard!
In Splunk, if you select a relative value from the Timestamp field in the Events table, you can then click any displayed event in the table to display a new tab with information about the affected system or policy.
However, if you select a real-time value from the Timestamp field, the displayed events do not respond when clicked. This is a limitation in Splunk. Splunk recommends that you avoid clicking real-time events to view event details.
A.3. Troubleshooting Hybrid Cloud Console integration with ServiceNow Copy linkLink copied to clipboard!
If ServiceNow is not receiving events from the Red Hat Hybrid Cloud Console, verify the configuration:
-
Ensure that the integration in the Red Hat Hybrid Cloud Console is enabled and has type
ServiceNow. -
Ensure that the integration in the Red Hat Hybrid Cloud Console has a correct URL. The URL should start with
https://<instance.servicenow.com>/api/x_rhtpp_rh_webhook/flow_templates_for_red_hat_insights. -
Ensure that the
x_rhtpp_rh_webhook.restuser role is defined in ServiceNow. Otherwise, notifications from the Hybrid Cloud Console will not work even if the application has been installed correctly. -
Ensure that the
rh_insights_integrationServiceNow user exists, is active, and has thex_rhtpp_rh_webhook.restrole assigned. -
If necessary, reset the password for the
rh_insights_integrationServiceNow user, and reset the user password in the integration on the Red Hat Hybrid Cloud Console.