Chapter 10. Command options for insights-client

You can use the insights-client command and its options to control the Insights client operation on your system. Because the insights-client.rpm is updated less frequently than individual components in Insights, the man page might not include the most recent information about insights-client command operation.

As a system administrator with root privileges, each time you enter the insights-client command the client collects data and sends it to Red Hat Insights.


Using the insights-client --display-name command to set the display name takes effect immediately but does not run the Insights client.

Table 10.1. insights-client user command options




Display help information


Register the host to Insights using the information in /etc/hostname. Will automatically enable the nightly cron job unless --disable-schedule is set.


Unregister the host from Insights.


Set or change the host display name in the GUI. Use with --register to set a display_name when the host is registered if you want a different name than is in /etc/hostname.


Add host to GROUP during registration. Group names are defined in /etc/insights-client/tags.yaml


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 the structure of the /etc/insights-client/remove.conf file.


Only log error messages to console.


Log nothing to console.


Enable the job schedule. By default, the Insights client runs daily, at or near midnight.

NOTE: If you are using Client 1.x, use the --register option to enable the schedule.


Disable the nightly job schedule.



Use a custom configuration file CONF instead of the default /etc/insights-client/insights-client.conf file.


Select the compressor that is used when creating the archive. Available options are gz, bz2, xz, none. Defaults to gz. The none option creates a tar file with no compression.


Runs the client but does not upload the archive to Red Hat Insights or CMSfR web application. The archive is stored in the /var/tmp/ directory. The file name is displayed when insights-client completes.


Run the client without using network functionality. Implies --no-upload.


Output the log data to the specified LOGFILE. The default log file is /var/log/insights-client/insights-client.log.


Fetch diagnostic information from the API. The system must be registered and uploaded at least once before using --diagnosis.


Scan the system with OpenSCAP and upload the report.


Upload a specific archive PAYLOAD file to Red Hat Insights. Requires --content-type.


Set the content-type for the PAYLOAD file. Type can be gz, bz2, xz, and none. The TYPE must match the --compressor used with the PAYLOAD.


Retrieve analysis results from Red Hat Insights.


Display analysis results fetched by --check-results.


Write collection to a specified directory instead of uploading.


Write collection to a specified archive instead of uploading.

The insights-client command has several options that are useful when debugging its operation.

Table 10.2. insights-client debug options



Print the versions of insights-client Client and Core.


Test connectivity to the Red Hat Insights services.


Re-register the system with Insights and use a new ID. This action duplicates an already-registered system.


Log all debug output to the console.


Runs the client but does not upload the archive. The archive is stored in the /var/tmp/ directory. The file name is displayed when insights-client completes.


Keep the archive after uploading.


Generate a diagnostic log for support.


Display host registration status.


Log network calls to the console.