Configuring and Using Hooks Notifications For Policies

Red Hat Insights 2020-04

How to configure and use hooks to notify on third-party applications

Red Hat Customer Content Services


This document demonstrates how to configure and use hooks in Policies to notify on third-party applications.
Providing Feedback:
If you have a suggestion to improve this document or find an error, submit a Bugzilla report at against Cloud Software Services ( for the Policies component.

Chapter 1. Overview


Hooks integration on is currently only available as Beta.

Webhooks, or simply hooks, enables Red Hat Insights to send event-driven notifications to a customer’s own hooks-compatible tooling, as those events happen. This frees administrators from having to routinely check into the Insights user interface, enabling a more event-driven monitoring strategy.

Policies integrate with Insights webhooks for their actions. Webhooks are responsible for sending POST messages as notifications to third-party applications that support incoming webhooks integration, such as instant messaging platforms, external ticketing systems among others. This provides users with the ability to integrate to their own operational workflow.


Chapter 2. Using hooks to notify on third-party applications

To assist operational management, you can use webhooks to notify on third-party applications that support incoming webhooks as an action for event-driven notification in policies, say, when system resources are configured above threshold, for example. Many commonly-used applications that are part of your daily workflow allow hooks integration.

Using hooks to notify on third-party applications requires:

  1. Configuring an incoming webhook in the third-party application.
  2. Adding a new hook via Red Hat Insights settings.
  3. Creating a new policy with Send to hook as the trigger action.

Chapter 3. Using hooks to notify on

This workflow example describes how to configure a hook and use it as an action in Policies to notify on allows you to test, inspect, forward and create custom actions for any incoming HTTP request or e-mail.

Note instantly generates a unique, random URL that you can use to test and debug Webhooks and HTTP requests, as well as to create your own workflows. So, no configuration is required to obtain an incoming webhook URL on

3.1. Adding a new hook via Settings

  1. In the beta platform, click Policies under Red Hat Insights.
  2. Click Settings settings gear , then select Hooks on the left-side menu.
  3. Click New hook.
  4. Enter a Name for the new hook.
  5. Enter the URL for the service you want to push notifications to. In this case, enter the randomly generated URL obtained on
  6. Under Triggers, select Policies, Triggered policies and All policies.
  7. Use the toggle switch located on the upper-right to activate the hook.
  8. Click Submit.

Your new hook is now added and listed on the Hooks page. Click the options menu options menu next to the hook and click Test. This will send a message to the endpoint URL as a test event. If the test event is successful, the status for the new hook you added will show Success with a green check mark. You can now create a new policy with the trigger action.

3.2. Creating a new policy with Send to hook as the trigger action

  1. In the beta platform, click Policies under Red Hat Insights.
  2. Click Create policy.
  3. On the Create Policy page, click From scratch or As a copy of existing Policy as required. Note that the As a copy of existing Policy option will prompt you to select a policy from the list of existing policies to use as a starting point.

    policy add

  4. Click Next.
  5. Enter a Name and Description for the policy.
  6. Click Next.
  7. Enter Condition. In this case, enter: facts.cloud_provider in [alibaba, aws, azure, google] and (facts.number_of_cpus >= 8 or facts.number_of_sockets >=2). This condition will detect if an instance running on the said public cloud providers are running with CPU hardware higher than the allowed limit.
  8. Click Validate condition, then click Next.
  9. On the Trigger actions page, click Add trigger actions and select Send to hook.
  10. Click Next.
  11. On the Review and activate page, click the toggle switch to activate the policy and review its details.
  12. Click Finish.

When the policy is evaluated on a system check-in, and if the condition in the policy is met, a notification will be sent to the configured hook using the endpoint URL, and hook settings added in Red Hat Insights. You will see the POST request logged instantly in with additional request details and the raw message content. offers Custom Action that allows additional processing and action on your requests.

Legal Notice

Copyright © 2020 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.