Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 7. Configuring notifications for inventory events

The Inventory service triggers four types of events:

  • Validation error
  • New system registered
  • System deleted
  • System became stale

Validation error events trigger when data in a payload from insights-client is not valid (corrupted data, incorrect values, or other issues). The validation process follows these steps:

  • insights-client runs on the system and generates a payload.
  • insights-client uploads the payload to the Hybrid Cloud Console.
  • The Hybrid Cloud Console receives the payload and validates it. The validation event triggers at this step. A validation error means that the payload cannot be processed, and that the console and Insights services cannot use its data.

The New system registered and System deleted events trigger when you register a new system in inventory, or when a system is removed from inventory (either manually or when it becomes stale and Insights automatically removes it).

System became stale events occur when a system changes state from active to inactive (stale). The Hybrid Cloud Console and Insights scan for system staleness every hour, and trigger staleness events for inactive systems. By default, Insights marks a system as stale if it remains inactive for 1 day. If the system remains inactive for 14 days, Insights marks the system as stale warning and schedules it for deletion.

A system can become stale due to inactivity, a lack of updates, disconnection, or decommissioning without proper retirement processes. This event indicates potential system maintenance issues.

For more information about system staleness and deletion, see Systems lifecycle in the inventory application.

You can configure notifications for these events using the Notifications service in the Red Hat Hybrid Cloud Console. The Notifications service enables you to configure responses to these events for your account. You can send email notifications to groups of users, or you can forward events to third-party applications, such as Splunk, ServiceNow, Event-Driven Ansible, Slack, Microsoft Teams, or Google Chat. You can also forward notifications, using a generic webhook with the Integrations service.

Note

To receive Notifications emails, users must subscribe to email notifications in their user preferences. Users may choose to receive each email notification individually, or they may subscribe to a daily digest email. For more information, refer to Configuring user preferences for email notifications.

The New system registered, System became stale, and System deleted events are particularly useful for driving automation, and for integrating Red Hat Insights into your operational workflows. For example, you can configure these events to automatically launch compliance or malware checks, validate systems assignments to Workspaces, update external CMDB records, or continuously monitor your RHEL environment.

Additional resources

7.1. Setting up organization notifications for inventory events
Copiar enlace

Note

Make sure that you configure third-party system integrations in the Hybrid Cloud Console, as well as any behavior groups that should receive inventory notifications. For more information about third-party system integrations, refer to Integrating the Red Hat Hybrid Cloud Console with third-party applications.

Prerequisites

  • You are logged in to the Red Hat Hybrid Cloud Console as a Notifications Administrator.

Procedure

  1. Navigate to Settings > Notifications > Configure Events.
  2. In the Configuration tab, select the Service filter.
  3. Click Filter by service, and then select Inventory from the drop-down list. The inventory events appear in the list of events.
  4. Select the event type you want to configure (for example, New system registered).
  5. To configure the event type, click the Edit (pencil) icon at the far right of the event type. A drop-down list displays with the list of available behavior groups configured in your organization.
  6. Select the checkboxes next to the behavior groups you want to configure for the Inventory event type.
  7. When you have finished selecting behavior groups, click the checkmark next to the list of behavior groups to save your selections.

Additional resources

7.2. Setting up user email notifications for inventory events
Copiar enlace

Note

Make sure to configure email preferences for each user to receive email notifications. For more information about how to set up user preferences, refer to Configuring user preferences for email notifications.

Prerequisites

  • You are a member of a user group that receives email notifications as part of a behavior group.
  • The behavior group is configured to trigger email notifications for your systems and to send those notifications to the user group to which you belong.

Procedure

  1. Navigate to Settings > Notifications > Notification Preferences.
  2. Select Inventory from the list of services. The list of available notifications for Inventory displays.
  3. Click the checkbox next to each type of notification you want to receive, or click Select All to receive all notifications for all Inventory events.
  4. Click Save.
Note

Configuring instant notifications might result in a large volume of email messages.

Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat