Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 4. Activate and open the subscriptions service


How to determine whether the subscriptions service activation is needed, how to activate the subscriptions service, log in, and verify access.

The subscriptions service must be activated to begin tracking usage for the Red Hat account for your organization. The activation process can be automatic or manual.

Review the following tasks that activate the subscriptions service automatically. If someone in your organization has completed one or more of these tasks, manual activation of the subscriptions service is not needed.

Note

These tasks, especially purchasing tasks, might be performed by a user that has the Organization Administrator (org admin) role in the Red Hat organization for your company. The integration creation tasks must be performed by a user with the Cloud administrator role in the role-based access control (RBAC) system for the Hybrid Cloud Console.

Procedure

  • Purchasing a pay-as-you-go On-Demand subscription for Red Hat OpenShift Container Platform or Red Hat OpenShift Dedicated through Red Hat Marketplace. As the pay-as-you-go clusters begin reporting usage through OpenShift Cluster Manager and the monitoring stack, the subscriptions service activates automatically for the organization.
  • Purchasing an Red Hat OpenShift pay-as-you-go On-Demand subscription through a cloud provider marketplace, such as Red Hat Marketplace or Amazon Web Services (AWS). Examples of these types of products include Red Hat OpenShift AI or Red Hat Advanced Cluster Security for Kubernetes. As these products begin reporting usage through the monitoring stack, the subscriptions service activates automatically for the organization.
  • Creating an Amazon Web Services integration through the integrations service in the Hybrid Cloud Console with the RHEL management bundle selected. The process of creating the integration also activates the subscriptions service.
  • Creating a Microsoft Azure integration through the integrations service in the Hybrid Cloud Console with the RHEL management bundle selected. The process of creating the integration also activates the subscriptions service.

    Note

    The integrations service was formerly known as the sources service in the Hybrid Cloud Console.

4.2. Activate the subscriptions service

If the subscriptions service is not activated by one of the tasks that include automatic activation, then the subscriptions service must be manually activated. Tasks that include automatic activation are purchasing an On-Demand subscription through Red Hat Marketplace or creating an Amazon Web Services or Microsoft Azure integration that includes the RHEL management bundle through the integrations service in the Hybrid Cloud Console.

If manual activation is needed, the subscriptions service must be activated by a user with access to the Red Hat account and organization through a Red Hat Customer Portal login. This login is not required to be a Red Hat Customer Portal Organization Administrator (org admin). In addition, that user must also have the Subscriptions administrator role or the Subscriptions viewer role in the user access role-based access control (RBAC) system for console.redhat.com.

Note

If a Red Hat Customer Portal login is associated with an organization that does not have an account relationship with Red Hat, then the subscriptions service cannot be activated.

When the subscriptions service is activated, the Hybrid Cloud Console tools begin analyzing and processing data from the data collection tools for display in the subscriptions service. Data processing for the initial display of the subscriptions service can take up to 24 hours. Until data for the account is ready, only an empty graph will display.

Note

The following procedure guides you through the steps to activate the subscriptions service from console.redhat.com. If the subscriptions service is not already activated, you can also access the activation page at the conclusion of the subscriptions service tour.

Procedure

  1. In a browser window, go to the Hybrid Cloud Console.
  2. If prompted, enter your Red Hat Customer Portal login credentials.
  3. In the Hybrid Cloud Console dashboard, click Services and then click Subscriptions and Spend in the navigation panel.
  4. On the Subscriptions and Spend page, click the Overview option for Subscription Services.
  5. In the navigation panel of the Subscription Services page, expand Subscriptions Usage.
  6. Click one of the Red Hat platform options, Red Hat Enterprise Linux, Red Hat OpenShift, or Ansible, to check the status of the subscriptions service for your Red Hat account and organization.
  7. If the subscriptions service is not yet active for the account, the activation page displays. Click Activate Subscriptions.
  8. If the subscriptions service is activated but not yet ready to display data, the subscriptions service application opens, but it displays an empty graph. Try accessing the subscriptions service later, typically the next day.
  9. If the subscriptions service is activated and the initial data processing is complete, the subscriptions service application opens and displays data on the graph. You can begin using the subscriptions service to view data about subscription usage and capacity for the account.

4.3. Log in to the subscriptions service

You access the subscriptions service from the Hybrid Cloud Console after logging in to your Red Hat Customer Portal login.

Procedure

  1. In a browser window, go to Hybrid Cloud Console.
  2. If prompted, enter your Red Hat Customer Portal login credentials.
  3. In the Hybrid Cloud Console dashboard, click Services and then click Subscriptions and Spend in the navigation panel.
  4. On the Subscriptions and Spend page, click the Overview option for Subscription Services.
  5. In the navigation panel of the Subscription Services page, expand Subscriptions Usage.
  6. Click one of the Red Hat platform options, Red Hat Enterprise Linux, Red Hat OpenShift, or Ansible, depending on the type of product usage that you want to view.

    Note

    If more than one product is generating usage for the subscriptions service, the platform page opens to a default view with a specific product variant or architecture in the Variant filter. Select another option in the Variant filter to view information about other architectures or product variants.

Verification

If the subscriptions service is activated and the initial data processing is complete, the subscriptions service opens and displays data on the graph. You can begin using the subscriptions service to view data about subscription usage and capacity for the account.

Note

If the subscriptions service opens but displays an empty graph, then the subscriptions service is activated but the initial data processing is not complete. Try accessing the subscriptions service later, typically the next day.

4.4. Verify access to the subscriptions service

User access to Hybrid Cloud Console services, including the subscriptions service, is controlled through a role-based access control (RBAC) system. User management capabilities for this RBAC system are granted to the Red Hat Organization Administrator (sometimes also referred to as org admin) for your Red Hat organization, and might also be granted to other members of the organization through the User Access administrator RBAC role. These user access administrators then manage the Hybrid Cloud Console RBAC groups, roles, and permissions for the other members in the organization by using the Settings > User Access option at console.redhat.com.

The predefined role Subscriptions viewer controls the ability to activate and access the subscriptions service. By default, every user in the organization has this role. However, if your Organization Administrator has made changes to user access roles and groups, you might not be able to access the subscriptions service.

Note

The RBAC system for the console.redhat.com contains two roles for the subscriptions service. The Subscriptions administrator role contains every available permission for the subscriptions service. The Subscriptions viewer role contains a subset of the permissions in the Subscriptions administrator role. An example of this type of user is one who only needs to view high-level report data, but does not need to view more detailed information about individual subscriptions and systems.

By default, all users are assigned the Subscriptions viewer role through the RBAC Default access group. However, the default behavior for role assignments is affected by how an organization is using RBAC groups to manage user access. If custom groups are in use instead of the Default access group, the Organization Administrator or another user with the User Access administrator RBAC role must manually update these groups to contain the new roles and manage any default assignment of them to the users in the organization.

Procedure

  • If you cannot activate or access the subscriptions service, contact your Organization Administrator. Your Organization Administrator can provide information about the status of the subscriptions service for your organization.

In the Hybrid Cloud Console, you can configure event notifications for Errata and Subscriptions Usage. The notifications are only sent for registered systems that have subscriptions for the product associated with them.

Part of subscription management is tracking updates, new releases of software, and subscription usage. When updates are available, from bug fixes to new releases, you can opt in to receive event notification alerts.

4.5.1. Errata event notifications

Errata event notifications are opt-in alerts for errata related to your subscriptions. These notifications include the following options:

  • Daily digest: Receive a daily summary of triggered application events that occur in a 24 hour time frame.
  • Instant notification: Receive an email immediately for each triggered application event. For errata alerts, instant notifications are batched and sent in 15-minute intervals.

    Important

    Some services do not offer both instant notification and daily digest. If you select Instant notification for any service, aside from Subscriptions Usage, you might receive a very large number of emails.

4.5.2. Configure Errata notifications

You can opt in to receive event notifications for Errata related to your subscriptions.

Note

Each user in the Hybrid Cloud Console must opt in to receive email notifications about events. You can select the services from which to receive notifications and the frequency.

Important

If you select Instant notification for any service, you might receive a very large number of emails.

Prerequisites

  • You are logged in to the Hybrid Cloud Console.

    Note

    You cannot log in to the Hybrid Cloud Console with your email address unless your email address is the same as your Red Hat login.

  • A Notifications administrator or Organization Administrator has configured behavior groups to receive event notifications.

Procedure

  1. In the Hybrid Cloud Console, navigate to Settings > Notifications > Notification Preferences. The My Notifications page is displayed. On the My Notifications page, the available services are grouped by category, for example OpenShift, Red Hat Enterprise Linux, or Subscriptions Services.
  2. Select Errata in the Subscriptions Services group. A list of the available event notifications for Errata | Subscription Services is displayed.
  3. At the top of the list, click Select all to enable all notifications for the service, or select one of the following options for each event listed:

    • Daily digest: Receive a daily summary of triggered application events that occur in a 24 hour time frame.
    • Instant notification: Receive an email immediately for each triggered application event. For errata alerts, instant notifications are batched and sent in 15-minute intervals.

      Important

      If you select Instant notification, you might receive a very large number of emails.

  4. Update your information and then click Save. Email notifications are delivered in the format and frequency that you selected.

    Note

    If you decide to stop receiving notifications, select Deselect all or clear the boxes for the events you do not want to be notified about, and then click Save. You will no longer receive any email notifications unless you return to this screen and enable them once again.

4.5.3. Subscriptions Usage event notifications

Subscriptions Usage event notifications evaluate usage against your threshold for a specific Service level and Usage within a product, or if applicable, for a product as a whole.

You can opt-in to alerts for when your organization has exceeded your subscription threshold. This notification includes the following option:

  • Instant Notification is the only option for Subscription usage.

    • The Subscription Usage notification alert triggers when your organization’s usage exceeds 105% of the subscription threshold.
    • The notification identifies Service level and Usage values in a product so you can match the alert to the correct subscription lines.

      • The Service level and Usage pair are system purpose values on your subscriptions, such as Premium and Production within that product.
    • For each distinct alert that applies to your account, you will receive one notification per month for as long as usage remains above 105% of the subscription threshold.
Note

Because each applicable Subscription Usage alert is sent once per month, you will not receive a second notification in the same month for that same scope even if you make adjustments to your account that resolve the over-usage condition.

The Subscription Usage event notification Behavior Group is set by default to send alerts to administrators.

Example scenario for Subscription Usage event notifications that will trigger an alert

The following example shows a RHEL subscription line where usage is compared to capacity for a specific Service level and Usage, and would trigger an alert.

  • An organization has one RHEL subscription with Premium / Production and 10 sockets.
  • Reported usage for sockets under Premium / Production for that product is 11.

In this case, usage for the Service level and Usage exceeds 105% of the subscribed capacity for that line, which would trigger an alert. The alert includes the Service level and Usage so you can view the correct subscriptions and metrics in the Hybrid Cloud Console, and plan adjustments for your account.

Example scenario for Subscription Usage event notifications that will not trigger an alert

The following is an example RHEL product subscription that demonstrates a situation where the usage is viewed by the product as a whole by the Subscription Usage event notification, and would not trigger the notification.

  • An organization has the following subscriptions:

    • 1 RHEL subscription with Premium / Production and 1 socket
    • 1 RHEL subscription with Standard / Development-Test and 100 sockets
  • The Subscription Usage event notification compares the total RHEL socket usage against 105 sockets.

Since the organization is using 100 sockets of RHEL premium, they will not be notified because the sum of all subscriptions is 101.

4.5.4. Configure Subscription Usage notifications

You can opt in to receive event notifications to alert you when subscription usage for your organization has exceeded your subscription threshold. Alerts apply to a specific Service level and Usage within that product so you know which subscription coverage is affected, or to a product as a whole if applicable.

The Subscription Usage notification is triggered when your organization’s usage exceeds 105% of the subscription threshold for a specific Service level and Usage in a product. For each applicable alert, the notification is sent once per month while the condition remains. These notifications can be used as a reminder to make adjustments to your account as needed.

The Subscription Usage event notification Behavior Group is set by default to send alerts to administrators.

Important

For a given Subscription Usage notification event, you will not receive a second alert in the same month if you make adjustments that resolve the over-usage that triggered the Subscription Usage notification event alert.

Prerequisites

  • You are logged in to the Hybrid Cloud Console.

    Note

    You cannot log in to the Hybrid Cloud Console with your email address unless your email address is the same as your Red Hat login.

Procedure

  1. In the Hybrid Cloud Console, navigate to Settings > Notifications > Notification Preferences. The My Notifications page is displayed. On the My Notifications page, the available services are grouped by category, for example OpenShift, Red Hat Enterprise Linux, or Subscriptions Services.
  2. Select Subscription Usage in the Subscriptions Services group. A list of the available event notifications for Subscription Usage | Subscription Services is displayed.
  3. At the top of the list, click Select all to enable all notifications for the service, or for Usage at 105% select:

    • Instant notification
  4. Update your information and then click Save.

    Note

    If you decide to stop receiving notifications, select Deselect all or clear the boxes for the events you do not want to be notified about, and then click Save. You will no longer receive any notifications unless you return to this screen and enable them once again.

Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red Hat
Retour au début