A significant portion of a system administrator’s tasks revolves around maintaining system health and ensuring operational efficiency. Red Hat Lightspeed provides proactive monitoring and analytics to help organizations manage their systems effectively. With the recent addition of new inventory events, operations teams can gain even deeper visibility into system life cycles, allowing them to automate responses and reduce manual intervention. By leveraging these events, organizations can trigger automated workflows, such as opening a ServiceNow ticket for new system registrations, escalating stale systems in PagerDuty, or initiating security remediations.

In this article, we will explore how event-driven architecture in Red Hat Lightspeed enhances system life cycle management. We will break down key inventory events, such as new system registrations, stale system detection, and system deletions. We’ll also discuss how you can configure notifications and alerts to stay ahead of potential issues. Finally, we will demonstrate how incorporating Red Hat Lightspeed events into your automation workflows can create self-healing systems, reduce manual workloads, and optimize operational efficiency.

Enabling proactive system management

Modern IT environments are constantly evolving, with systems undergoing frequent changes due to operating system updates, patches for newly discovered vulnerabilities, and varying workload demands. Traditional monitoring approaches often rely on periodic checks, which can lead to delays in detecting critical system state changes. Event-driven architecture shifts system management from passive monitoring to real-time, proactive responses.

At its core, event-driven architecture enables systems or management tooling to emit events whenever significant changes occur. These events can then trigger automated workflows, notifications, or remediation actions, reducing the need for manual intervention. In the context of Red Hat Lightspeed, and in particular the inventory service, this means IT teams can receive timely updates when systems are registered, stale, or deleted. This allows them to take proactive steps to maintain system health.

Event-driven monitoring in Red Hat Lightspeed

Event-driven automation can help organizations:

• Reduce downtime: Address issues before they affect users and systems.
• Improve security posture: Detect inactive systems early to prevent vulnerabilities.
• Streamline operations: Automate registration, patching, and decommissioning tasks.

Red Hat Lightspeed provides event-driven capabilities that allow organizations to closely monitor their systems inventory and respond quickly to changes. By using Red Hat Lightspeed, IT teams can gain visibility into their system’s life cycle and automate workflows for faster, more efficient management.

In this article, we will focus our attention on the Red Hat Lightspeed inventory service, but other applications within Red Hat Lightspeed also trigger events that can be leveraged for operations. For those of you new to Red Hat Lightspeed and its inventory, we recommend reading the official product documentation on viewing and managing system inventory.

Events triggered from Red Hat Lightspeed inventory provide information about the system life cycle. These events reflect significant changes within the Red Hat Lightspeed inventory, which serves as the central repository for all system data and services.

The key events you can expect to receive include:

• New system registered (which happens first in a system’s life cycle): This event is triggered whenever a new system is added to your inventory. It helps ensure that systems are properly tracked and managed from the moment they are registered. This event can trigger workflows for initial system configuration, policy application, or further system validation checks.
• System became stale (mid-life cycle monitoring): A system is considered stale when it has not been reported for a certain time in the inventory, often due to inactivity, a lack of updates, a disconnection, or decommissioning without proper retirement processes. This event highlights potential system maintenance issues and can automatically trigger actions, such as notifying administrators or initiating the first steps to diagnose and reactivate Red Hat Lightspeed on the system.
• System deleted (end of life cycle): When a system is removed from your inventory, an event is triggered to indicate the deletion. This helps you track system decommissioning and ensure that no systems are left unmanaged. Deleting systems may also trigger specific workflows for resource reallocation, Configuration Management Database (CMDB) updates, or automated archiving tasks.

These events are a powerful tool for IT teams, as they provide valuable data to help keep track of system status and life cycle progression.

The anatomy of inventory events

To effectively leverage the power of Red Hat Lightspeed events, it is important to understand their structure and how they are triggered. Each event is designed to provide you with specific, actionable information about the system’s life cycle, helping you stay proactive with your operations. Let’s take a closer look at the event structure that you would receive.

New system registered

When a new system is added to Red Hat Lightspeed inventory, this event is triggered. Systems are added when a collector discovers or registers them. You can find a list of data collectors and their upload frequencies in the Red Hat Lightspeed inventory documentation. This will help you understand how often updates are received and processed.

The following is an example of what you would expect to receive as a result of a new registration using the insights client on a system.

{
"account_id":null,
"application":"inventory",
"bundle":"rhel",
"context":{
"inventory_id":"04e36dd4-de82-4843-ba82-d5226f550c21",
"hostname":"rhel8desktop",
"display_name":"rhel8desktop",
"rhel_version":"8.7",
"tags":{"insights-client":{"Owner":["Jerome Marc"],"Application":["RHEL Desktop"]}},
"host_url":"https://console.redhat.com/insights/inventory/04e36dd4-de82-4843-ba82-d5226f550c21"},
"event_type":"new-system-registered",
"events":[{
"metadata":{},
"payload":{
"groups":[],
"insights_id":"f6e15c55-e0d5-4609-94c6-b925b40ee087",
"subscription_manager_id":"f6e15c55-e0d5-4609-94c6-b925b40ee087",
"satellite_id":"",
"reporter":"puptoo",
"system_check_in":"2025-03-03T10:58:10.571119+00:00"}}],
"org_id":"7931872",
"timestamp":"2025-03-03T10:58:10.631454",
"source":{
"application":{"display_name":"Inventory"},
"bundle":{"display_name":"Red Hat Enterprise Linux"},
"event_type":{"display_name":"New system registered"}}
}

All Red Hat Lightspeed events follow the same schema definition, with key elements such as bundle, application, event_type, and timestamp allowing users or applications to understand the source of the event. The context and payload fields (located under events) provide additional information about the system responsible for triggering the event and any associated findings related to the event respectively. In the case of a New system registered event, we get system details such as an inventory_id, hostname, or even a list of tags for this system. The payload contains data related to the method of registration under reporter (e.g., puptoo for the insights client) and various foreign IDs for this system (e.g., subscription_manager_id and satellite_id) that could be useful in your automation. You can find more information about Red Hat Lightspeed HTTP POST messages and their structure in the product documentation.

With this event triggered on new registration, you can set up notifications to alert administrators, open a ServiceNow ticket for tracking, or trigger automated actions like applying configuration templates, running initial security audits, or logging details in Splunk for analysis.

System became stale

A system is marked as stale when it has been inactive or disconnected from the inventory for an extended period of time. The default is set to 24 hours, but you can modify this configuration in Red Hat Lightspeed by changing the system staleness and deletion time limits at the account level. More information about this operation is available in the Red Hat Lightspeed inventory product documentation:

{
"account":null,
"application": "inventory",
"bundle": "rhel",
"context": {
"inventory_id": "04e36dd4-de82-4843-ba82-d5226f550c21",
"hostname": "rhel8desktop",
"display_name": "rhel8desktop",
"rhel_version": "8.7",
"tags": {"insights-client":{"Owner":["Jerome Marc"],"Application":["RHEL Desktop"]}},
"host_url": "https://console.redhat.com/insights/inventory/04e36dd4-de82-4843-ba82-d5226f550c21"},
"event_type": "system-became-stale",
"events": [{
"metadata": {},
"payload": {
"groups": [],
"insights_id": "f6e15c55-e0d5-4609-94c6-b925b40ee087",
"subscription_manager_id": "f6e15c55-e0d5-4609-94c6-b925b40ee087",
"satellite_id": ""}}],
"org_id": "3340851",
"timestamp": "2025-03-04T12:01:23.631454+00:00",
"source":{
"application":{"display_name":"Inventory"},
"bundle":{"display_name":"Red Hat Enterprise Linux"},
"event_type":{"display_name":"System became stale"}}
}

This event helps detect systems that may be out of compliance or are at risk of becoming vulnerable due to inactivity, as well as flag any systems that have been decommissioned without properly being removed from the Red Hat Lightspeed inventory or CMDB. For example, you could implement a workflow to automatically prompt users for troubleshooting in Microsoft Teams, schedule patching for updates, or notify security teams by creating an incident in ServiceNow for review.

System deleted

When a system is removed from your inventory, a System deleted event is triggered. This can occur when a user or script initiates the operation, or automatically when a system exceeds its staleness warning period and is purged from the inventory. More details on the system staleness life cycle are available in the Red Hat Lightspeed product documentation.

{
"account_id":null,
"application":"inventory",
"bundle":"rhel",
"context":{
"inventory_id":"422bee07-9544-43de-b617-c8a16afa6272",
"hostname":"rhel8desktop",
"display_name":"rhel8desktop",
"rhel_version":"8.7",
"tags":{"insights-client":{"Owner":["Jerome Marc"],"Application":["RHEL Desktop"]}},
"event_type":"system-deleted",
"events":[{
"metadata":{},
"payload":{
"groups":[],
"insights_id":"733d53e6-1e6d-4ee2-94dd-67926a87710f",
"subscription_manager_id":"733d53e6-1e6d-4ee2-94dd-67926a87710f",
"satellite_id":""}}],
"org_id":"7931872",
"timestamp":"2024-08-15T13:03:33.004981",
"source":{
"application":{"display_name":"Inventory"},
"bundle":{"display_name":"Red Hat Enterprise Linux"},
"event_type":{"display_name":"System deleted"}}
}

This event ensures that all systems removed from your Red Hat Lightspeed inventory are accounted for, helping with proper inventory management, compliance tracking, and resource reallocation.

As we have seen, each event provides granular data you can leverage to automate responses, drive workflows, and improve decision-making. By understanding the anatomy of these events, you will be in a better position to use them effectively within your operational workflows.

How to configure notifications and alerts

Configuring notifications and alerts is key to maximizing the value of Red Hat Lightspeed events. With the right alerts in place, you will be able to stay informed of critical system changes and take action before they escalate. With a well-defined notification strategy, you can automate responses, reduce manual intervention, and streamline your operational workflows. For example, you can send an alert to administrators via Slack or Microsoft Teams, or automatically create an incident in ServiceNow when a system is deleted.

Let’s walk through how to configure these notifications for various events in Red Hat Lightspeed. The following steps outline how to configure Red Hat Lightspeed events notifications for your organization. These steps are fully documented in the Red Hat Hybrid Cloud Console product documentation. You must be a notifications administrator to perform these actions.

1. In Hybrid Cloud Console, go to Settings (gear icon) and select Notifications.
2. Under Configure Events, select the Red Hat Enterprise Linux bundle tab.
3. Click the Behavior groups tab and select Create new group.
4. Follow the creation wizard, providing a name and description for your group.
5. Under Actions and recipients, expand the Action dropdown and select Send an email.

Choose recipients from the **Recipients **dropdown list. This includes All (for all users), Admins (for administrators only), or any User Access groups defined in your organization. You can select one or more groups to receive email notifications.

Optional: You can also configure notifications to send to integration endpoints for real-time alerts and workflow automation:

• A webhook endpoint for any generic integration to third-party applications.
• Communication tools like Slack, Microsoft Teams, or Google Chat.
• Reporting and automation tools such as Event-Driven Ansible (part of Red Hat Ansible Automation Platform), PagerDuty, ServiceNow, or Splunk.
• If these integrations are not yet configured, you can add them later in Settings > Integrations.
• For more details, refer to the Integrating the Red Hat Hybrid Cloud console with third-party applications documentation.

1. In the next Associate event types step of the wizard, select the relevant Red Hat Lightspeed application and events to trigger notifications. For this article, choose life cycle events triggered by the Inventory application: New system registered, System became stale, and System deleted.
2. The final screen provides a summary of the new behavior groups. Click Finish to validate and create the behavior group for your organization.

Note:

For email notifications, individual users must subscribe to alerts through their user preferences in the Hybrid Cloud Console. They can choose between instant notifications or daily summaries for each event type. The steps for configuring user preferences are documented in the Hybrid Cloud Console product documentation.

Integrate Red Hat Lightspeed events into operational workflows

Integrating Red Hat Lightspeed events into your operational workflows allows you to transform your IT operations into a more proactive, automated framework. Rather than reacting to issues when they arise, you can anticipate and address potential problems before they impact system performance or security.

By using integrations with tools like Event-Driven Ansible, you can automate actions and responses such as:

• Registering or removing a system from an external CMDB.
• Applying templates for post-provisioning automation, including assigning the system to a security profile and scanning it for vulnerabilities.
• Automatically patching a system to make sure it is up to date with latest advisories.
• Triggering a script or playbook to re-enable a system that has been disconnected for too long.
• Executing a decommissioning workflow when a system is deleted for automatic resource cleanup, such as redistributing subscriptions/licenses or releasing IP addresses.

By combining event alerts with automated workflows, you can create a self-healing infrastructure, where systems automatically detect and resolve issues without manual intervention. This minimizes downtime and optimizes system performance.

Many organizations rely on a mix of tools and platforms for system management. To get the most value from your Red Hat Lightspeed events, you can implement cross-platform workflows that extend beyond Red Hat Lightspeed such as:

• Service management tools: When a system becomes stale, automatically open a ticket in ServiceNow or Jira for an administrator to review, reducing manual tracking and expediting issue resolution.
• Cloud management systems: When a system is deleted, your workflow might include triggering actions in your cloud management platform, such as releasing cloud resources or rebalancing workloads.
• Security tools: To catch vulnerabilities early, use event-driven workflows to automatically trigger security scans or audits whenever a system is marked as stale or deleted.

By bridging multiple systems, you can create a unified, cohesive response to events, thereby reducing gaps in your operational workflow.

Next steps

As your IT operations evolve, tapping into the full potential of Red Hat Lightspeed events will ensure your infrastructure remains agile, secure, and optimized, all while reducing manual workloads and fostering improved team collaboration.

The benefits of leveraging Red Hat Lightspeed inventory events are clear:

• Proactive system management through real-time alerts and automated responses.
• Improved security by identifying stale or outdated systems that need immediate attention.
• Streamlined workflows that integrate seamlessly with existing tools and processes.
• Enhanced reporting and compliance by ensuring that systems are consistently maintained and tracked.

Ready to implement Red Hat Lightspeed events in your organization? Start by enabling notifications in the Hybrid Cloud Console and integrating event-driven workflows using Ansible Automation Platform. For more guidance, check out the Red Hat Lightspeed and Event-Driven Ansible playlists on YouTube. You can also try Ansible Automation Platform free for 60 days.