.Improved metrics for RHOSO Observability You can now use new metrics for monitoring the health of RHOSO services, including the following: * `kube_pod_status_phase` * `kube_pod_status_ready` * `node_systemd_unit_state` * `podman_container_state` * `podman_container_health` You can use the `kube_pod_status_phase` and `kube_pod_status_ready` to monitor control plane services. * `kube_pod_status_phase` - The relevant parameter is `Phase`, with values of Pending, Running, Succeeded, Failed, or Unknown, and corresponding Boolean values of `1` or `0`. * `kube_pod_status_ready` - This metric also has Boolean values, with `1` indicating that the pod has all the containers running and readiness probes succeeding, and `0` indicating that the pod has not all the containers running or that the readiness probe did not succeed. You can use the `node_systemd_unit_state` to monitor the running state of data plane services. * `node_systemd_unit_state ` - The relevant parameter is `State`, with values of activating, active, deactivating, failed, inactive, and corresponding Boolean values of `1` or `0`. You can use the `podman_container_state` and `podman_container_health` to monitor the health of data plane containerized services.   * `podman_container_state` - This metric can have the following values: -1=unknown, 0=created, 1=initialized, 2=running, 3=stopped, 4=paused, 5=exited, 6=removing, 7=stopping. * `podman_container_health` - This metric can have the following values: -1=unknown, 0=healthy, 1=unhealthy, 2=starting.