Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 3. Set up the subscriptions service for data collection

How to set up the environment for the subscriptions service data collection, connect your Red Hat Enterprise Linux, Red Hat OpenShift, and Red Hat Ansible systems to the Hybrid Cloud Console services through one or more data collection tools.

3.1. Install Red Hat Lightspeed
Copiar enlace

Install Red Hat Lightspeed to collect information about your inventory.

Procedure

  • Install the Red Hat Lightspeed client on every RHEL system that is managed by Red Hat Satellite by using the following instructions:

    • Red Hat Lightspeed on Satellite Red Hat Enterprise Linux (RHEL)

      Note

      The Red Hat Lightspeed client is installed by default on RHEL 8 and later systems unless the minimal installation option was used to install RHEL. However, the client must still be registered, as documented in the client installation instructions.

3.1.1. Red Hat Lightspeed data collection
Copiar enlace

When the Red Hat Lightspeed client is installed on a system, it collects data about that system on a daily basis and sends it to the Red Hat Insights cloud application. The data might also be shared with other applications on the Hybrid Cloud Console, such as inventory or the subscriptions service services. Red Hat Lightspeed provides configuration and command options, including options for data obfuscation and data redaction, to manage that data.

See Additional resources to examine the types of data that Red Hat Lightspeed collects and sends to Red Hat or add controls to the data that is sent, including:

  • The use of the insights-client --offline command to generate an offline dump of the data before you register a system to Red Hat Lightspeed.
  • The use of the insights-client --no-upload command to run a test data collection process
  • The use of the remove.conf file and its options to exclude specific data from collection based on file, command, pattern, and keyword settings.

3.2. Install the Satellite inventory upload plugin
Copiar enlace

When you are using Red Hat Satellite as a data collection tool for the subscriptions service, you must use the Satellite inventory upload plugin in combination with the virt-who tool for accurate reporting of hypervisor host-guest mapping information for Red Hat Enterprise Linux virtual data center (VDC) subscriptions and similar virtualized environments. The use of this plugin enables the uploading of host-based data from Satellite into the inventory service and enables the association of hosts with guests and with the Satellite instance that manages them. If the plugin is not enabled, the subscriptions service cannot accurately report usage for RHEL virtualized subscriptions.

Note

The plugin is also required by other Hybrid Cloud Console applications. In addition to the requirement for the inventory service of Red Hat Lightspeed to enable the uploading of host inventory information, the plugin is also required for the remediations service of Red Hat Lightspeed to enable remediation actions from both Satellite and Red Hat Lightspeed.

After the Satellite inventory upload plugin is enabled, it is active for every Satellite organization, including existing and newly created organizations.

Prerequisites

  • Red Hat Satellite 6.9 or later (versions that are under full support)

Procedure

  • For a new installation of Satellite

    For a new installation of Satellite, the Satellite inventory upload plugin is installed and enabled by default. No action is required to enable it.

  • For upgraded Satellite

    For Satellite that is upgraded to a currently supported version, the Satellite inventory upload plugin is installed. However, you might have to enable the plugin.

    • If the plugin was previously enabled for Satellite before the upgrade, it remains enabled. No action is required to enable it.

    • If the plugin was not enabled for Satellite before the upgrade, then you must enable it.

      1. In the Satellite web interface, expand the Configure options and select Red Hat Inventory.

      2. Follow the instructions on the Red Hat Inventory page to enable the Automatic inventory upload option for Satellite.

        Note

        When the Automatic inventory upload option is enabled, the Satellite inventory upload plugin automatically reports once per day by default. You can also manually send data and view the status of the extract and upload actions for individual Satellite organizations.

        The Satellite inventory upload plugin includes reporting settings that you can use to address data privacy concerns. Use the options on the Red Hat Inventory page to configure the plugin to exclude certain packages, obfuscate host names, and obfuscate host addresses.

3.3. Register systems to Red Hat Subscription Management
Copiar enlace

If you are using Red Hat Subscription Management as the data collection tool, register your RHEL systems to Red Hat Subscription Management. Systems that are registered to Red Hat Subscription Management can be found and tracked by the subscriptions service.

Some RHEL images can use the autoregistration feature of the RHEL management bundle and do not have to be manually registered to Red Hat Subscription Management. However, the following specific requirements must be met:

  • The image must be based on RHEL 8.4 and later or 8.3.1 and later.
  • The image must be an Amazon Web Services (AWS) or Microsoft Azure cloud services image.
  • The image can be a Cloud Access Gold Images image or a custom image, such as an image built with Image Builder. If it is a custom image, the subscription-manager tool in the image must be configured to use autoregistration.

  • The image must be associated with an AWS or Azure integration, as configured from the Settings > Integrations option in the Hybrid Cloud Console, with the RHEL management bundle selected for activation.

    Note

    The integrations service was formerly known as the sources service in the Hybrid Cloud Console. The image must be provisioned after this integration is created.

  • The image must be provisioned after this integration is created.

RHEL systems that do not meet these requirements must be registered manually to be tracked by the subscriptions service.

Procedure

  • Register your RHEL systems to Red Hat Subscription Management, if not already registered. For more information about this process, see the following information:

3.4. Connect Red Hat OpenShift to the subscriptions service
Copiar enlace

If you use Red Hat OpenShift products, the steps you must do to connect the correct data collection tools to the subscriptions service depend on multiple factors. These factors include the installed version of Red Hat OpenShift Container Platform and Red Hat OpenShift Dedicated, whether you are working in a connected or disconnected environment, and whether you are using Red Hat Enterprise Linux, Red Hat Enterprise Linux CoreOS, or both as the operating system for clusters.

The subscriptions service is designed to work with customers who use Red Hat OpenShift in connected environments. One example of this customer profile is using Red Hat OpenShift Container Platform 4.1 and later with an Annual subscription with connected clusters. For this customer profile, Red Hat OpenShift has a robust set of tools that can perform the data collection. The connected clusters report data to Red Hat through Red Hat OpenShift Cluster Manager, Telemetry, and the other monitoring stack tools to supply information to the data pipeline for the subscriptions service.

Customers with disconnected Red Hat OpenShift Container Platform 4.1 and later environments can use Red Hat OpenShift as a data collection tool by manually creating each cluster in Red Hat OpenShift Cluster Manager.

Customers who use Red Hat OpenShift 3.11 can also use the subscriptions service. However, for Red Hat OpenShift version 3.11, the communication with the subscriptions service is enabled through other tools that supply the data pipeline, such as Red Hat Lightspeed, Satellite, or Red Hat Subscription Management.

Note

For customers who use Red Hat OpenShift Container Platform or Red Hat OpenShift Dedicated 4.7 and later with a pay-as-you-go On-Demand subscription (available for connected clusters only), data collection is done through the same tools as those used by Red Hat OpenShift Container Platform 4.1 and later with an Annual subscription.

Complete the following steps, based on your version of Red Hat OpenShift Container Platform and the cluster operating system for worker nodes.

Procedure

  • Red Hat OpenShift Container Platform 4.1 or later with Red Hat Enterprise Linux CoreOS

    For this profile, cluster architecture is optimized to report data to Red Hat OpenShift Cluster Manager through the Telemetry tool in the monitoring stack. Therefore, setup of the subscriptions service reporting is essentially confirming that this monitoring tool is active.

    • Make sure that all clusters are connected to Red Hat OpenShift Cluster Manager through the Telemetry monitoring component. If so, no additional configuration is needed. The subscriptions service is ready to track Red Hat OpenShift Container Platform usage and capacity.

  • Red Hat OpenShift Container Platform 4.1 or later with a mixed environment with Red Hat Enterprise Linux CoreOS and Red Hat Enterprise Linux

    For this profile, data gathering is affected by the change in the Red Hat OpenShift Container Platform reporting models between Red Hat OpenShift major versions 3 and 4. Version 3 relies upon RHEL to report RHEL cluster usage at the node level. This is still the reporting model used for version 4 RHEL nodes. However, the version 4 era reporting model reports Red Hat Enterprise Linux CoreOS usage at the cluster level through Red Hat OpenShift tools.

    The tools that are used to gather this data are different. Therefore, the setup of the subscriptions service reporting is to confirm that both tool sets are configured correctly.

    1. Make sure that all clusters are connected to Red Hat OpenShift Cluster Manager through the Red Hat OpenShift Container Platform Telemetry monitoring component.
    2. Make sure that Red Hat Enterprise Linux nodes in all clusters are connected to at least one of the Red Hat Enterprise Linux data collection tools, Red Hat Lightspeed, Satellite, or Red Hat Subscription Management. For more information, see the instructions about connecting to each of these data collection tools in this guide.

  • Red Hat OpenShift Container Platform version 3.11

    Red Hat OpenShift Container Platform version 3.11 reports cluster usage based on the Red Hat Enterprise Linux nodes in the cluster. Therefore, for this profile, the subscriptions service reporting uses the standard Red Hat Enterprise Linux data collection tools.

    • Make sure that all Red Hat Enterprise Linux nodes in all clusters are connected to at least one of the Red Hat Enterprise Linux data collection tools, Red Hat Lightspeed, Satellite, or Red Hat Subscription Management. For more information, see the instructions about connecting to each of these data collection tools in this guide.

3.5. Connect cloud integrations to the subscriptions service
Copiar enlace

Data collection for certain pay-as-you-go On-Demand subscriptions requires a connection known as a cloud integration, configured with the integrations service of the Hybrid Cloud Console.

A cloud integration on the Red Hat Hybrid Cloud Console is a connection to a service, application, or provider that supplies data to another Hybrid Cloud Console service. Through a cloud integration, the connected service can connect with and use data from public cloud providers and other services or tools to collect data for that service.

Note

When a cloud integration is required to track the usage of a subscription, the post-purchase enablement steps generally include information about this requirement. These post-purchase enablement instructions might contain more current information about setting up the cloud integration.

The following products require the configuration of a cloud integration to enable data collection for the subscriptions service:

  • Red Hat Enterprise Linux for Third Party Linux Migration with Extended Life Cycle Support Add-on, metered with the the cost management service method

    If you want to use the cost management service to meter the usage of RHEL for Third Party Linux Migration with ELS in the subscriptions service, you must create a cloud integration. The configuration of a cloud integration for includes a creating a connection between a cloud provider and the cost management service in the Hybrid Cloud Console. This cloud integration ensures that usage data from the cloud provider and from the cost management service is used to calculate metered usage in the subscriptions service and that usage data is returned to the cloud provider for billing purposes.

    The post-purchase enablement steps for RHEL for Third Party Linux Migration with ELS include information about setting up the required cloud integration, in addition to other setup information required for the subscription. To ensure that your cloud integration is configured correctly for use by the subscriptions service, review the following information and confirm that the cloud integration configuration steps were completed.

Procedure

Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

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.

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 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.

Legal Notice

Theme

© 2026 Red HatVolver arriba