Assessing RHEL Configuration Issues Using the Red Hat Insights Advisor Service

Red Hat Insights 2022

Assess and monitor the configuration issues impacting your RHEL systems

Red Hat Customer Content Services

Abstract

Use the Insights Advisor service to assess and monitor configuration issues affecting the availability, stability, performance, and security of your RHEL systems.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Overview of Insights for Red Hat Enterprise Linux advisor service assessment and monitoring

Use the advisor service to assess and monitor the health of your Red Hat Enterprise Linux (RHEL) infrastructure. Whether you are concerned with individual or groups of systems, or with your whole infrastructure, be aware of the exposure of your systems to configuration issues that can affect availability, stability, performance, and security.

After installing and registering the Insights for Red Hat Enterprise Linux client, the client runs daily to check systems against a database of Recommendations, which are sets of conditions that can leave your RHEL systems at risk. Your data is then uploaded to the Red Hat Enterprise Linux > Advisor > Recommendations page where you can perform the following actions:

  • See all of the recommendations for your entire RHEL infrastructure.
  • Use robust filtering capabilities to refine your results to those recommendations, systems, groups, or workloads that are of greatest concern to you, including SAP workloads, Satellite host collections, and custom tags.
  • Learn more about individual recommendations, details about the risks they present, and get resolutions tailored to your individual systems.
  • Share results with other stakeholders. For more information, see Generating Advisor Service Reports.
  • Create and manage remediation playbooks to fix issues right from the Insights for Red Hat Enterprise Linux application. For more information, see Remediating Configuration Issues Using Red Hat Insights and Ansible Playbooks.

Chapter 2. Advisor service recommendations overview

The advisor service bundles information about known configuration issues that might negatively affect the availability, stability, performance, or security of your RHEL systems. This information bundle is used to create recommendations about how you can fix or remediate issues on your systems. (A recommendation was formerly called a rule in Red Hat Insights for Red Hat Enterprise Linux.) Recommendations are published to the advisor service database, and can be accessed through the advisor recommendations page.

When you navigate to the recommendations page you can use various sort and filter methods to access information such as:

  • Modified. Shows the date or time frame when a recommendation was last modified (or published) to the advisor service database.
  • Category. Shows the type of issue or what the issue affects—​whether the issue has the potential to negatively affect the availability, stability, performance, or security of RHEL systems.
  • Impact. Shows the impact (Low, Medium, High or Critical) on system operations if an incident related to the recommendation were to happen.
  • Incidents. Shows the issue has been classified as an incident and is an issue that is already affecting your systems.
  • Likelihood. Shows the likelihood (Low, Medium, High or Critical) that the issue will negatively affect your infrastructure.
  • Name. Shows a brief description of the issue, including how it affects RHEL systems.
  • Reboot Required. Shows whether a system reboot is required (Required or Not Required) as part of remediation steps.
  • Remediation. Shows if the fix or remediation requires manual steps or has an automated playbook.
  • Risk of change. Shows the risk of change (Very Low, Low, Moderate, or Important) for systems if a remediation is executed.
  • Status. Describes a recommendation’s status. (All, Enabled, Disabled, or Red Hat disabled).

    • All. Shows results for all status options.
    • Enabled and Disabled. Show business-critical recommendations that are visible, or not visible. A disabled recommendation indicates that someone in your organization turned the visibility of a recommendation off.
    • Red Hat disabled. Shows recommendations that Red Hat makes available for you to enable when you are performing specific actions, like upgrading Red Hat Enterprise Linux major versions.
  • Systems or Systems impacted. Shows the number of systems (1 or more or None) on which a recommendation is detected. 1 or more systems shows one or more systems that have recommendations. None Shows systems that do not have recommendations.
  • Total risk. Describes total risk level (Low, Moderate, Important, or Critical), which is determined by the likelihood that the issue will negatively affect your infrastructure, and the impact on system operations if that were to happen.

The default advisor service recommendations view shows a smaller subset of information. The information is filtered to show recommendation information for one or more systems. These recommendations have a status of Enabled. For information about using filters, see Filtering recommendations.

2.1. System and recommendation pairing

When a recommendation exists on a system, the advisor service identifies whether, and how, the system has been impacted and provides specific mitigation or resolution instructions. This information is visible when viewing a recommendation and then selecting an affected system.

After selecting an affected system, view all recommendations available for the system along with the following information:

  • Detected issues. Specific information about the fault on that system
  • Steps to resolve. Steps to resolve the issue on that system
  • Related knowledgebase articles. KB articles or solutions about the general issue
  • Additional info. Other support articles on the issue or solutions for resolution
  • Ansible. Playbook remediation availability

Chapter 3. Refining advisor service recommendations

The advisor service puts a lot of information at your fingertips, especially when Red Hat Insights for Red Hat Enterprise Linux is deployed on a large Red Hat Enterprise Linux infrastructure. There are several ways to refine advisor recommendations to help you focus on the issues and systems that matter the most. This section describes the multiple options for filtering, sorting, and excluding specific recommendations from your advisor results.

img adv recommendations filters updated

3.1. Viewing all advisor recommendations

When you first enter the advisor service recommendations view, you see the default view and results of Systems Impacted (set to 1 or more systems) and Status (set to Enabled) filters being applied. To get a comprehensive view of all recommendations, including those not impacting your systems and those in the advisor database, use the following procedure:

Prerequisites

*You must be logged into the Red Hat Hybrid Cloud Console.

Procedure

  1. Navigate to the Red Hat Enterprise Linux > Advisor > Recommendations page.
  2. Click the close icon img insights close next to the Systems Impacted and Status filters. You can now browse through all of the potential recommendations for your systems.
  3. Optionally, return to the default recommendations view that shows 1 or more of Systems impacted and the Status set to Enabled, by clicking Reset filters.

3.2. Filtering recommendations

Select from the following filters to refine your recommendations list:

  • Name. In the subfilter field, start typing the recommendation description or a keyword and select from the options presented.
  • Total risk. In the subfilter field, select from one or more: Critical, Important, Moderate, or Low.
  • Risk of change. In the subfilter field, select from High, Moderate, Low, or Very low.
  • Impact. In the subfilter field, select from Critical, Important, Moderate, or Low.
  • Likelihood. In the subfilter field, select from Critical, Important, Moderate, or Low.
  • Category. In the subfilter field, select from Availability, Performance, Stability, or Security.
  • Incidents. In the subfilter field, select to show recommendations with or without incidents having occurred.
  • Remediation. In the subfilter field, select Ansible playbook or Manual for the remediation method.
  • Reboot required. In the subfilter field, select either Required or Not required.
  • Ansible support. In the subfilter field, select to show recommendations with or without Ansible Playbook support.
  • Status. In the subfilter field, select from All, Enabled, Disabled, Red Hat disabled.
  • Systems impacted. In the subfilter field, select either 1 or more or None.

To set filters, complete the following steps.

Procedure

  1. Navigate to the Red Hat Enterprise Linux > Advisor > Recommendations page and log in if necessary.
  2. Click the filter icon and select a filter category from the dropdown list.

    img adv set filters updated

  3. Click the dropdown arrow in the subfilter menu and check a box (or boxes) to activate a subfilter or, in the case of Description, begin typing the name or description of a recommendation.

    img adv set subfilter updated

3.3. Recommendations table columns and sorting

Sort columns in the advisor recommendations table using the following parameters:

  • Name. Alphabetize by A to Z or Z to A.
  • Modified. Order by number of days since the recommendation was last modified or published, from newest or oldest.
  • Total risk. View in order of criticality.
  • Systems. View by the number of your systems that are impacted.
  • Remediation. Sort by recommendations that have or do not have Ansible Playbook support.

3.4. Disabling a recommendation

Disable specific recommendations impacting your systems so that they no longer appear in your results. To disable a recommendation, complete the following steps:

Procedure

  1. Navigate to the Red Hat Enterprise Linux > Advisor > Recommendations page and log in if necessary.
  2. Locate the recommendation to disable.
  3. Click the More-options icon ( img insights more actions icon ) at the right end of the row and then click Disable recommendation.

3.5. Viewing and enabling a previously disabled recommendation

When a recommendation is disabled, you will no longer see the recommendation in your advisor results. To reverse this action, complete the following steps:

Procedure

  1. Navigate to the Red Hat Enterprise Linux > Advisor > Recommendations page and log in if necessary.
  2. Click the Filter dropdown and select Status.
  3. In the subfilter dropdown list, select Disabled.

    img adv enable disabled rec updated

  4. Locate the recommendation to enable.
  5. Click the more-actions icon, img insights more actions icon , on the right side of the row, and click Enable recommendation.

    img adv enable rec updated

Chapter 4. Using pathways to resolve multiple recommendations

4.1. About pathways

A pathway is a group of advisor-service recommendations that share a common resolution. By following the remediation steps in a pathway, you can view and address multiple recommendations in one configuration change. This enables you to see all of the systems that the remediation affects without having to investigate every action within every recommendation. Pathways present clear paths to follow to maintain your systems more efficiently.

The specific recommendations that appear in a pathway depend on the issues that affect your infrastructure at a given time. Insights for Red Hat Enterprise Linux dynamically calculates remediation levels based on the most significant recommendations in your environment. The calculation includes the following factors:

  • number of systems impacted by individual recommendations
  • total risk of individual recommendations
  • whether there is an incident detected

Issues grouped into pathways must share the same common resolution type, such as a package update, configuration update, product upgrade, and so on. In addition, the issues must share a common resolution target. Each system must require the same package update or configuration file change.

Insights for Red Hat Enterprise Linux names each pathway after its core remediation, so you can immediately see and understand the configuration change.

4.2. Viewing and assessing advisor pathways

Prerequisites

Procedure

  1. Navigate to Red Hat Insights > Advisor > Recommendations. The Recommended Pathways panel appears at the top of the page, and includes up to three of the most significant pathways for your systems.

    img pathways overview

  2. To view details for a pathway, click View Pathway, or click Pathways in the list of recommendations and then click the pathway from the list. The information for the pathway appears.

    img pathways view pathway2

  3. To view the systems that the issue affects (and which are included in the list of systems that the pathway remediates), click Systems.

    img pathways affected systems

4.3. Remediating pathways

Prerequisites

  • Root-level access to your systems.
  • Organization Administrator-level access to Insights.
  • If you are using Ansible playbooks for remediations, you need user access to Ansible.

Procedure

  1. Navigate to Red Hat Insights > Advisor > Recommendations.
  2. Locate the pathway you want to remediate and click View Pathway.
  3. Select a recommendation to remediate, or click Systems to see a list of all of the affected systems.
  4. To view more information about each recommendation, expand the table row for the recommendation, or click the recommendation title and navigate to the Recommendation Details page.
  5. Select the systems you want to remediate, and then click Remediate.

    1. If the remediation requires an Ansible playbook, follow the steps in the Remediate with Ansible dialog box to create or select a playbook and select the systems to remediate.
    2. If the remediation requires manual remediation, follow the Steps to resolve procedure to perform the remediation on each of the selected systems.
Note

If the remediation shows System reboot is required, Ansible automatically reboots the affected system (or systems) after the remediation is complete.

4.4. Configuring notifications for recommendations

You can receive notifications of new available recommendations through the Insights Notifications service.

Note

You can receive notifications for individual recommendations in a pathway, but not for the pathway itself. To view the pathway associated with a recommendation, log in to the console.

Prerequisites

  • Root-level access to your systems.
  • Organization Administrator-level access to Insights.

Procedure

  1. Navigate to Settings > Notifications > Red Hat Enterprise Linux. The available behavior groups appear.
  2. Select an existing behavior group or create a new one.
  3. Click the Options menu icon (vertical dots) for the behavior group and select Edit. The Edit behavior group wizard appears.
  4. Review the behavior group name and click Next. The Actions and recipients page appears.
  5. Review the actions and recipients and click Next. The Associate event types page appears.
  6. Select New recommendation to add it to the behavior group. Click Next.
  7. Review the updated settings for the behavior group and click Finish.

Chapter 5. Refining the advisor service Systems list

The Systems view shows all of your systems that have the Insights client installed and reporting advisor data. The Systems list can be refined in the following ways.

img adv systems filters

5.1. Filter by name

Search for the host or system name.

5.2. Sorting options

Use the sorting arrows above the following columns to order your systems table:

  • Name. Alphabetize by A to Z or Z to A.
  • Number of recommendations. Order by the number of recommendations impacting each system.
  • Last seen. Order by the number of minutes, hours, or days since an archive was last uploaded from the system to the advisor service.

Chapter 6. Filtering tags, SAP workloads, and groups in the advisor service

Filter results in the advisor service UI by custom group tags, SAP workloads, and Satellite groups to quickly locate and view the systems you want to focus on.

In the advisor service, access tag, workload, and group filters using the Filter results box, located in the upper left corner of the page in the Red Hat Insights for Red Hat Enterprise Linux application.

The filter dropdown menu shows all of the tags associated with the account, allowing you to click one or more parameters by which to filter. To filter by tags in the advisor service, complete the following steps:

Procedure

  1. Navigate to the Red Hat Enterprise Linux > Advisor > Systems page and log in if necessary. The Filter results box is in most views in the Red Hat Insights for Red Hat Enterprise Linux application and these procedures work anywhere you access Filter results.
  2. Click the arrow on the Filter results box and scroll to see the tags available for systems on this account.
  3. Select one or more tags to filter by SAP workloads, Satellite host group, or a custom group. Applied tags are visible next to the Filter results box.
  4. View the filtered results throughout the advisor service.
  5. To remove the tag, click Clear filters.

Chapter 7. Deleting a system from inventory

You can delete a system from the Red Hat Hybrid Cloud Console inventory so that the system is no longer visible in the Red Hat Insights for Red Hat Enterprise Linux Inventory or advisor service Systems list. The Insights client will be unregistered on the system and no longer report data to Red Hat Insights for Red Hat Enterprise Linux. To delete a system, complete the steps in the procedure below that is most relevant to your use case.

Procedure 1: Delete using the Insights client

  1. Enter the following command on the system command line:

    [root@server ~]# insights-client --unregister

Procedure 2: Delete from the Red Hat Satellite 6 UI

  1. Log in to the Satellite web UI.
  2. Navigate to Insights > Inventory.
  3. Select the system profile to be unregistered.
  4. Click Actions > Unregister.

Procedure 3: Delete using the cloud.redhat.com API

Use this option only when the actual system is destroyed/re-installed. If you use the DELETE API without unregistering the client, hosts will reappear the next time the client uploads data.

  1. Get the list of system profiles from inventory.

    # curl -k --user PORTALUSERNAME https://cloud.redhat.com/api/inventory/v1/hosts | json_pp > hosts.json
  2. If the json_pp command does not exist on the system then install the perl-JSON-PP package.

    # yum install perl-JSON-PP
  3. Get the ID of the system from the hosts.json file and confirm system details; for example, "id" : "f59716a6-5d64-4901-b65f-788b1aee25cc".

    # curl -k --user PORTALUSERNAME https://cloud.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
  4. Delete the system profile using the following command:

    # curl -k --user PORTALUSERNAME -X "DELETE" https://cloud.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc

Chapter 8. System tags and groups

Red Hat Insights for Red Hat Enterprise Linux enables administrators to filter groups of systems in inventory and in individual services using group tags. Groups are identified by the method of system data ingestion to Insights for Red Hat Enterprise Linux. Insights for Red Hat Enterprise Linux enables filtering groups of systems by those running SAP workloads, by Satellite host group, by Microsoft SQL Server workload, and by custom tags that are defined by system administrators with root access to configure the Insights client on the system.

Note

As of Spring 2022, inventory, advisor, compliance, vulnerability, patch, drift, and policies enable filtering by groups and tags. Other services will follow.

Important

Unlike the other services that enable tagging, the compliance service sets tags within lists of systems in the compliance service UI. For more information, see Group and tag filters in the compliance service.

Use the global, Filter results box to filter by SAP workloads, Satellite host groups, MS SQL Server workloads, or by custom tags added to the Insights client configuration file.

Prerequisites

The following prerequisites and conditions must be met to use the tagging features in Red Hat Insights for Red Hat Enterprise Linux:

  • The Red Hat Insights client is installed and registered on each system.
  • To create custom tags, root permissions, or their equivalent, are required to add to or change the /etc/insights-client/tags.yaml file.

8.1. SAP workloads

As Linux becomes the mandatory operating system for SAP ERP workloads in 2025, Red Hat Enterprise Linux and Red Hat Insights for Red Hat Enterprise Linux are working to make Insights for Red Hat Enterprise Linux the management tool of choice for SAP administrators.

As part of this ongoing effort, Insights for Red Hat Enterprise Linux automatically tags systems running SAP workloads and by SAP ID (SID), without any customization needed by administrators. Users can easily filter those workloads throughout the Insights for Red Hat Enterprise Linux application by using the global Filter by tags drop-down menu.

8.2. Satellite host groups

Satellite host groups are configured in Satellite and recognized automatically by Insights for Red Hat Enterprise Linux.

8.3. Microsoft SQL Server workloads

Using the global Filter by tags feature, Red Hat Insights for Red Hat Enterprise Linux users can select groups of systems running Microsoft SQL Server workloads.

In May of 2019, the Red Hat Insights team introduced a new set of Insights for Red Hat Enterprise Linux recommendations for Microsoft SQL Server running on Red Hat Enterprise Linux (RHEL). These rules alert administrators to operating system level configurations that do not conform to the documented recommendations from Microsoft and Red Hat.

A limitation of these rules was that they primarily analyzed the operating system and not the database itself. The latest release of Insights for Red Hat Enterprise Linux and RHEL 8.5, introduces Microsoft SQL Assessment API. The SQL Assessment API provides a mechanism to evaluate the database configuration of MS SQL Server for best practices. The API is delivered with a rule set containing best practice rules suggested by the Microsoft SQL Server Team. While this rule set is enhanced with the release of new versions, the API is built with the intent to give a highly customizable and extensible solution, which enables users to tune the default rules and create their own.

The SQL Assessment API is supported by PowerShell for Linux (available from Microsoft), and Microsoft has developed a PowerShell script that can be used to call the API and store its results as a JSON formatted file. With RHEL 8.5, the Insights client now uploads this JSON file and presents the results in an easy-to-understand format in the Insights for Red Hat Enterprise Linux UI.

For more information about SQL Server assessment in Insights for Red Hat Enterprise Linux, see SQL Server database best practices now available through Red Hat Insights.

8.3.1. Setting up SQL Server assessments

To configure the Microsoft SQL Assessment API to provide information to Red Hat Insights, the database administrator needs to take the following steps.

Procedure

  1. In the database you wish to assess, create a login for SQL Server assessments using SQL Authentication. The following Transact-SQL creates a login. Replace <*PASSWORD*> with a strong password:

    USE [master]
    GO
    CREATE LOGIN [assessmentLogin] with PASSWORD= N'<*PASSWORD*>’
    ALTER SERVER ROLE [sysadmin] ADD MEMBER [assessmentLogin]
    GO
  2. Store the credentials for login on the system as follows, again replacing <*PASSWORD*> with the password you used in step 1.

    # echo "assessmentLogin" > /var/opt/mssql/secrets/assessment
    # echo "<*PASSWORD*>" >> /var/opt/mssql/secrets/assessment
  3. Secure the credentials used by the assessment tool by ensuring that only the mssql user can access the credentials.

    # chmod 0600 /var/opt/mssql/secrets/assessment
    # chown mssql:mssql /var/opt/mssql/secrets/assessment
  4. Download PowerShell from the microsoft-tools repository. This is the same repository you configured when you installed the mssql-tools and mssqlodbc17 packages as part of SQL Server installation.

    # yum -y  install powershell
  5. Install the SQLServer module for PowerShell. This module includes the assessment API.

    # su mssql -c "/usr/bin/pwsh -Command Install-Module SqlServer"
  6. Download the runassessment script from the Microsoft examples GitHub repository. Ensure it is owned and executable by mssql.

    # /bin/curl -LJ0 -o /opt/mssql/bin/runassessment.ps1 https://raw.githubusercontent.com/microsoft/sql-server-samples/master/samples/manage/sql-assessment-api/RHEL/runassessment.ps1
    # chown mssql:mssql /opt/mssql/bin/runassessment.ps1
    # chmod 0700 /opt/mssql/bin/runassessment.ps1
  7. Create the directory that will store the log file used by Red Hat Insights. Again, make sure it is owned and executable by mssql.

    # mkdir /var/opt/mssql/log/assessments/
    # chown mssql:mssql /var/opt/mssql/log/assessments/
    # chmod 0700 /var/opt/mssql/log/assessments/
  8. You can now create your first assessment, but be sure to do so as the user mssql so that subsequent assessments can be run automatically via cron or systemd more securely as the mssql user.

    # su mssql -c "pwsh -File /opt/mssql/bin/runassessment.ps1"
  9. Insights for Red Hat Enterprise Linux will automatically include the assessment next time it runs, or you can initiate Insights client by running this command:

    # insights-client

8.3.1.1. Setting up the SQL Assessment on a timer

Because SQL Server Assessments can take 10 minutes or more to complete, it may or may not make sense for you to run the assessment process automatically every day. If you would like to run them automatically, the Red Hat SQL Server community has created systemd service and timer files to use with the assessment tool.

Procedure

  1. Download the following files from Red Hat public SQL Server Community of Practice GitHub site.

    • mssql-runassessment.service
    • mssql-runassessment.timer
  2. Install both files in the directory /etc/systemd/system/:

    # cp mssql-runassessment.service /etc/systemd/system/
    # cp mssql-runassessment.timer /etc/systemd/system/
    # chmod 644 /etc/systemd/system/
  3. Enable the timer with:

    # systemctl enable --now mssql-runassessment.timer

8.4. Custom system tagging

By applying custom grouping and tagging to your systems, you can add contextual markers to individual systems, filter by those tags in the Insights for Red Hat Enterprise Linux application, and more easily focus on related systems. This functionality can be especially valuable when deploying Insights for Red Hat Enterprise Linux at scale, with many hundreds or thousands of systems under management.

Note

To create custom tags, root permissions, or their equivalent, are required to add to or change the /etc/insights-client/tags.yaml file.

8.4.1. Tag structure

Tags use a namespace/key=value paired structure.

  • Namespace. The namespace is the name of the ingestion point, insights-client, and cannot be changed. The tags.yaml file is abstracted from the namespace, which is injected by the Insights client before upload.
  • Key. The key can be a user-chosen key or a predefined key from the system. You can use a mix of capitalization, letters, numbers, symbols and whitespace.
  • Value. Define your own descriptive string value. You can use a mix of capitalization, letters, numbers, symbols and whitespace.

8.4.2. Creating a tags.yaml file and adding a custom group

Create and add tags to /etc/insights-client/tags.yaml simply by using insights-client --group=<name-you-choose>, which performs the following actions:

  • Creates the etc/insights-client/tags.yaml file
  • Adds the group= key and <name-you-choose> value to tags.yaml
  • Uploads a fresh archive from the system to the Insights for Red Hat Enterprise Linux application so the new tag is immediately visible along with your latest results

After creating the initial group tag, add additional tags as needed by editing the /etc/insights-client/tags.yaml file.

The following procedure shows how to create the /etc/insights-client/tags.yaml file and the initial group, then verify the tag exists in the Insights for Red Hat Enterprise Linux inventory.

Procedure to create new group

  1. Run the following command as root, adding your custom group name after --group=:

    [root@server ~]# insights-client --group=<name-you-choose>

Example of tags.yaml format

The following example of a tags.yaml file shows an example of file format and additional tags added for the new group:

# tags
---
group: eastern-sap
name: Jane Example
contact: jexample@corporate.com
Zone: eastern time zone
Location:
- gray_rack
- basement
Application: SAP

Procedure to verify your custom group was created

  1. Navigate to Red Hat Enterprise Linux > Inventory and log in if necessary.
  2. Click the Filter results dropdown menu.
  3. Scroll through the list or use the search function to locate the tag.
  4. Click the tag to filter by it.
  5. Verify that your system is among the results on the advisor systems list.
  6. Procedure to verify the system is tagged
  7. Navigate to Red Hat Enterprise Linux > Inventory and log in if necessary.
  8. Activate the Name filter and begin typing the system name until you see your system, then select it.
  9. Verify that, next to the system name, the tag symbol is darkened and shows a number representing the correct number of tags applied.

8.4.3. Editing tags.yaml to add or change tags

After creating the group filter, edit the contents of /etc/insights-client/tags.yaml as needed to add or modify tags.

Procedure

  1. Using the command line, open the tag configuration file for editing.

    [root@server ~]# vi /etc/insights-client/tags.yaml

  2. Edit content or add additional values as needed. The following example shows how you can organize tags.yaml when adding multiple tags to a system.

    # tags
    ---
    group: eastern-sap
    location: Boston
    description:
    - RHEL8
    - SAP
    key 4: value
    Note

    Add as many key=value pairs as you need. Use a mix of capitalization, letters, numbers, symbols, and whitespace.

  3. Save your changes and close the editor.
  4. Optionally, generate an upload to Insights for Red Hat Enterprise Linux.

    # insights-client

Chapter 9. Reference materials

To learn more about Red Hat Insights for Red Hat Enterprise Linux, the following resources might also be of interest:

Providing feedback on Red Hat documentation

We appreciate your feedback on our documentation. To provide feedback, highlight text in a document and add comments.

Prerequisites

  • You are logged in to the Red Hat Customer Portal.
  • In the Red Hat Customer Portal, the document is in the Multi-page HTML viewing format.

Procedure

To provide your feedback, perform the following steps:

  1. Click the Feedback button in the top-right corner of the document to see existing feedback.

    Note

    The feedback feature is enabled only in the Multi-page HTML format.

  2. Highlight the section of the document where you want to provide feedback.
  3. Click the Add Feedback pop-up that appears near the highlighted text.

    A text box appears in the feedback section on the right side of the page.

  4. Enter your feedback in the text box and click Submit.

    A documentation issue is created.

  5. To view the issue, click the issue link in the feedback view.

Legal Notice

Copyright © 2023 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 http://creativecommons.org/licenses/by-sa/3.0/. 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.