4.5.5. Running an Insights Operator gather operation on-demand
Instead of waiting for the next periodic data gather operation, you can run a custom on-demand Insights Operator data gather operation by using the OpenShift Container Platform web console or command-line interface (CLI).
A periodic data gather operation uses the InsightsDataGather custom resource definition (CRD) for configuration instructions, whereas an on-demand equivalent requires a DataGather CRD to be configured.
An on-demand DataGather operation is:
-
Useful for one-off data collections that require different CRD configurations to the periodic data gathering (
InsightsDataGather) specification. -
Independent from the periodic data gathering. When you create an on-demand
DataGatherCRD, the configuration is independent from theInsightsDataGatherCRD specification of your periodic data gathering job.
Custom specification options
You can optionally customize the following items for the on-demand data gather operation:
-
Enable and define data obfuscation: By defining the
DataGatherdataPolicyspecification, you can enable additional obfuscation of the Red Hat Lightspeed archive data, for example, the IP address or workload names. -
Enable persistant storage: By default, the Insights Operator uses ephemeral storage, which means that a new pod will be created for each gather operation and the history of gather operations and data collected is not retained. You can switch to persistent storage to retain the data and history for up to the last 10 gather operations by defining the
DataGatherstoragespecification in the CRD. -
Exclude specific data gather operations: You can choose to disable specific gather operations from running by defining the
DataGathergatherersspecification. For example, you can choose to disable the cluster authentication operation or the workload data operation.
Excluding gather operations from the default list might reduce or limit the recommendations offered by the Red Hat Lightspeed advisor service for your cluster.
If you do not configure any custom specification options in the DataGather CRD, the default Insights Operator data collection job will run. This means that all gather operations will run, the collected data will be unobfuscated and the archive file will not be retained.
When you run a gather operation on-demand, any configuration that was previously applied to disable Insights Operator gather operations for your cluster will be overridden.
The DataGather custom resource is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
If you enable Technology Preview in your cluster, the Insights Operator runs gather operations in individual pods. This is part of the Technology Preview feature set for the Insights Operator and supports the new data gathering features.
4.5.5.1. Viewing Insights Operator gather durations 링크 복사링크가 클립보드에 복사되었습니다!
You can view the time it takes for the Insights Operator to gather the information contained in the archive. This helps you to understand Insights Operator resource usage and issues with Red Hat Lightspeed Advisor.
Prerequisites
- A recent copy of your Insights Operator archive.
Procedure
From your archive, open
/insights-operator/gathers.json.The file contains a list of Insights Operator gather operations:
{ "name": "clusterconfig/authentication", "duration_in_ms": 730, "records_count": 1, "errors": null, "panic": null }The
duration_in_msfield is the amount of time in milliseconds for each gather operation.- Inspect each gather operation for abnormalities.