This is a cache of https://docs.openshift.com/rosa/support/remote_health_monitoring/using-insights-operator.html. It is a snapshot of the page at 2024-11-25T03:06:37.019+0000.
Using Insights Operator - Remote health monitoring with connected clusters | Support | Red Hat OpenShift <strong>service</strong> on AWS
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Using the Insights Operator

edit

The Insights Operator periodically gathers configuration and component failure status and, by default, reports that data every two hours to Red Hat. This information enables Red Hat to assess configuration and deeper failure data than is reported through Telemetry. Users of Red Hat OpenShift service on AWS can display the report in the Insights Advisor service on Red Hat Hybrid Cloud Console.

Additional resources
edit

Understanding Insights Operator alerts

The Insights Operator declares alerts through the Prometheus monitoring system to the Alertmanager. You can view these alerts in the Alerting UI in the Red Hat OpenShift service on AWS web console by using one of the following methods:

  • In the Administrator perspective, click Observe → Alerting.

  • In the Developer perspective, click Observe → <project_name> → Alerts tab.

Currently, Insights Operator sends the following alerts when the conditions are met:

Table 1. Insights Operator alerts
Alert Description

InsightsDisabled

Insights Operator is disabled.

SimpleContentAccessNotAvailable

Simple content access is not enabled in Red Hat Subscription Management.

InsightsRecommendationActive

Insights has an active recommendation for the cluster.
edit

Obfuscating Deployment Validation Operator data

Cluster administrators can configure the Insight Operator to obfuscate data from the Deployment Validation Operator (DVO), if the Operator is installed. When the workload_names value is added to the insights-config ConfigMap object, workload names—rather than UIDs—are displayed in Insights for Openshift, making them more recognizable for cluster administrators.

Prerequisites

  • Remote health reporting is enabled, which is the default.

  • You are logged in to the Red Hat OpenShift service on AWS web console with the "cluster-admin" role.

  • The insights-config ConfigMap object exists in the openshift-insights namespace.

  • The cluster is self managed and the Deployment Validation Operator is installed.

Procedure

  1. Go to Workloads → ConfigMaps and select Project: openshift-insights.

  2. Click on the insights-config ConfigMap object to open it.

  3. Click Actions and select Edit ConfigMap.

  4. Click the YAML view radio button.

  5. In the file, set the obfuscation attribute with the workload_names value.

    apiVersion: v1
kind: ConfigMap
# ...
data:
  config.yaml: |
    dataReporting:
      obfuscation:
        - workload_names
# ...

  6. Click Save. The insights-config config-map details page opens.

  7. Verify that the value of the config.yaml obfuscation attribute is set to - workload_names.