anchor.diff:  - **xref:../monitoring/cluster-monitoring/about-cluster-monitoring.adoc#about-cluster-monitoring[Monitor clusters]**:
   Learn to  xref:../monitoring/cluster-monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[configure the monitoring].
   Once your monitoring is configured, use the Web UI to access xref:../monitoring/cluster-monitoring/prometheus-alertmanager-and-grafana.adoc#prometheus-alertmanager-and-grafana[Prometheus, Alertmanager, and Grafana].
  -To monitor applications, configure custom metrics for each selected namespace.
  +In addition to infrastructure metrics, you can also scrape and view metrics for your own services.
   
   - **xref:../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring_about-remote-health-monitoring[Remote health monitoring]**: {product-title} collects anonymized aggregated information about your cluster and reports it to Red Hat via Telemetry and the Insights Operator. This information allows Red Hat to improve {product-title} and to react to issues that impact customers more quickly. You can view the xref:../support/remote_health_monitoring/showing-data-collected-by-remote-health-monitoring.adoc#showing-data-collected-by-remote-health-monitoring_showing-data-collected-by-remote-health-monitoring[data collected by remote health monitoring].
   endif::[]
  
positive.code: ifdef::openshift-dedicated[]
  == Cluster administrator activities
  
  While cluster maintenance and host configuration is performed by the OpenShift
  Operations Team, other ongoing tasks on your {product-title} {product-version}
  cluster can be performed by {product-title} cluster administrators. As a
  {product-title} cluster administrator, this documentation will help you:
  
negative.code: documentation will help you:
  
  - **xref:../architecture/architecture.adoc#architecture-overview-architecture[Understand {product-title} management]**: Learn about components
  of the {product-title} {product-version} control plane. See how {product-title} masters and workers are managed and updated through the xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#machine-api-overview_creating-machineset-aws[Machine API] and xref:../operators/olm-what-operators-are.adoc#machine-api-overview-architecture[Operators].
  
  === Manage cluster components
  
  - **Manage machines**: Manage machines in your cluster on
  xref:../machine_management/creating_machinesets/creating-machineset-aws.adoc#creating-machineset-aws[AWS],
  xref:../machine_management/creating_machinesets/creating-machineset-azure.adoc#creating-machineset-azure[Azure],
  or
  xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#creating-machineset-gcp[GCP]
  by xref:../machine_management/deploying-machine-health-checks.adoc#deploying-machine-health-checks[deploying health checks] and xref:../machine_management/applying-autoscaling.adoc#applying-autoscaling[applying autoscaling to machines].
  
  - **xref:../registry/registry-options.adoc#registry-options[Manage container registries]**: Each {product-title} cluster includes a built-in container registry for storing its images. You can also configure a separate link:https://access.redhat.com/documentation/en-us/red_hat_quay/[Red Hat Quay] registry to use with {product-title}. The link:https://quay.io[Quay.io] site provides a public container registry that stores {product-title} containers and Operators.
  
  - **xref:../authentication/understanding-authentication.adoc#understanding-authentication[Manage users and groups]**: Add users and groups that have different levels of permissions to use or modify clusters.
  
  