Options for insights-client command
As a system administrator with root privileges, you can use the insights-client command and its options to control the insights-client operation on your system.
Updates to the insights-client.rpm occur less often than updates to individual components in Red Hat Lightspeed. The frequency of updates could cause the man page to not include the most recent information about insights-client.
Each time you enter the insights-client command, the client collects data and sends it to Red Hat Lightspeed.
insights-client --display-name command to set the display name takes effect immediately, but does not run the insights-client.| Option | Description |
|---|---|
|
|
Display help information |
|
|
Register the host to Red Hat Lightspeed by using the information in |
|
|
Unregister the host from Red Hat Lightspeed. |
|
|
Set or change the host display name in the GUI.
Use it with the |
|
|
Add a host to a GROUP during registration. Define Group names in |
|
|
Set the number of times to retry an upload. The default is 1. The retry interval is 180 seconds, which is how long the insights-client waits until retrying the upload. NOTE: In the scheduler, the number of retries is 3. |
|
|
Validate |
|
|
Log only error messages to the terminal output. |
|
|
Disable message logging to the terminal. |
|
|
Enable the job schedule. By default, the insights-client runs daily, at or near midnight. |
|
|
Disable the nightly job schedule. |
|
|
Use a custom configuration file by specifying a file path for CONF instead of using the default IMPORTANT: This option is not available for RHEL 10 systems. |
|
|
Runs the insights-client without uploading the archive to Red Hat Lightspeed. The archive is stored in the |
|
|
Run the client without using network functionality. Using this command does not upload data to Red Hat Lightspeed, similar to using the |
|
|
Write the log data to the specified log file. The default log file is IMPORTANT: This option is not available for RHEL 10 systems. |
|
|
Get diagnostic information from the API. The system must be registered and uploaded at least once to use the |
|
|
Scan the system with OpenSCAP and upload the report to the Red Hat Lightspeed compliance service in the Red Hat Hybrid Cloud Console. |
|
|
List the policies available to assign to the system. The output also provides information for the following categories:
|
|
|
Assign the system to the policy by using the ID from the |
|
|
Remove the system from the policy by using the ID from the |
|
|
Upload a specific archive payload file to Red Hat Lightspeed. You must set |
|
|
Set the content type for the |
|
|
Display analysis results by using the |
|
|
Write the collection to a specified directory instead of uploading to Red Hat Lightspeed. |
|
|
Write the collection to a specified archive instead of uploading to Red Hat Lightspeed. |
|
|
Set or change the Ansible hostname in Red Hat Lightspeed inventory. Run this during registration to specify a different hostname from the one listed in |
|
|
Show |
|
|
Refresh the system package manager cache. |
|
|
The specified manifest YAML file that defines what Red Hat Lightspeed Core should collect. |
|
|
Do a lightweight check-in instead of a full upload. |
|
|
Run the specified application and upload its generated archive. For example, specify:
|
Additionally, use the following insights-client command options when you need to debug insights-client operations:
| Option | Description |
|---|---|
|
|
Print the versions of |
|
|
Test connectivity to the Red Hat Lightspeed services. |
|
|
Log all debug output to the console. |
|
|
Run the client, but do not upload the archive. The client stores the archive in the |
|
|
Store the archive in the |
|
|
Generate a diagnostic log for support. |
|
|
Display host registration status. |
|
|
Log network calls to the console. |