This is a cache of https://docs.openshift.com/container-platform/4.15/support/remote_health_monitoring/enabling-remote-health-reporting.html. It is a snapshot of the page at 2024-11-22T11:40:21.190+0000.
Enabling remote health reporting - Remote health monitoring with connected clusters | Support | OpenShift Container Platform 4.15
    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
×

Enabling remote health reporting

If you or your organization have disabled remote health reporting, you can enable this feature again. You can see that remote health reporting is disabled from the message "Insights not available" in the Status tile on the OpenShift Container Platform Web Console Overview page.

To enable remote health reporting, you must Modify the global cluster pull secret with a new authorization token.

Enabling remote health reporting enables both Insights Operator and Telemetry.

Modifying your global cluster pull secret to enable remote health reporting

You can modify your existing global cluster pull secret to enable remote health reporting. If you have previously disabled remote health monitoring, you must first download a new pull secret with your console.openshift.com access token from Red Hat OpenShift Cluster Manager.

Prerequisites

  • Access to the cluster as a user with the cluster-admin role.

  • Access to OpenShift Cluster Manager.

Procedure

  1. Navigate to https://console.redhat.com/openshift/downloads.

  2. From Tokens → Pull secret, click Download.

    The file pull-secret.txt containing your cloud.openshift.com access token in JSON format downloads:

    {
  "auths": {
    "cloud.openshift.com": {
      "auth": "<your_token>",
      "email": "<email_address>"
    }
  }
}

  3. Download the global cluster pull secret to your local file system.

    $ oc get secret/pull-secret -n openshift-config --template='{{index .data ".dockerconfigjson" | base64decode}}' > pull-secret

  4. Make a backup copy of your pull secret.

    $ cp pull-secret pull-secret-backup

  5. Open the pull-secret file in a text editor.

  6. Append the cloud.openshift.com JSON entry from pull-secret.txt into auths.

  7. Save the file.

  8. Update the secret in your cluster.

    oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=pull-secret

It may take several minutes for the secret to update and your cluster to begin reporting.

Verification

  1. Navigate to the OpenShift Container Platform Web Console Overview page.

  2. Insights in the Status tile reports the number of issues found.