All System Management Health services are exposed outside the cluster through the OAuth2 Proxy and Istio’s ingress gateway to enforce the authentication and authorization policies. The URLs to access these services are available on any system with CMN, BGP, MetalLB, and external DNS properly configured.
The SYSTEM_DOMAIN_NAME value found in some of the URLs on this page is expected to be the system’s fully qualified domain name (FQDN).
(ncn-mw#) The FQDN can be found by running the following command on any Kubernetes NCN.
kubectl get secret site-init -n loftsman -o jsonpath='{.data.customizations\.yaml}' | base64 -d | yq r - spec.network.dns.external
Example output:
system.hpc.amslabs.hpecorp.net
Be sure to modify the example URLs on this page by replacing SYSTEM_DOMAIN_NAME with the actual value found using the above command.
Access any System Management Health service with the provided links.
When accessing the URLs listed below, it will be necessary to accept one or more browser security warnings in order to proceed to the login screen and navigate through the application after successfully logging in. The details of the security warning will indicate that a self-signed certificate/unknown issuer is being used for the site. Support for incorporation of certificates from Trusted Certificate Authorities is planned for a future release.
URL: https://vmselect.cmn.SYSTEM_DOMAIN_NAME/select/0/prometheus/vmui
Vmagent instance scrapes metrics from Kubernetes, Ceph, and the hosts (part of victoria-metrics-k8s-stack Helm chart).
VictoriaMetrics generates alerts based on metrics and reports them to the Alertmanager. The ‘Alerts’ link at the top of the page will show all of the inactive, pending, and firing alerts on the system.
Clicking on any of the alerts will expand them, enabling users to use the ‘Labels’ data to discern the details of the alert. The details will also show the state of the alert, how long it has been
active, and the value for the alert.
For more information regarding the use of the VictoriaMetrics interface, see Getting Started/ in the VictoriaMetrics online documentation.
Some alerts may be falsely triggered. This occurs if they are alerts which will be improved in the future, or if they are alerts impacted by whether all software products have been installed yet. See Troubleshoot Prometheus Alerts.
URL: https://vmselect.cmn.SYSTEM_DOMAIN_NAME/select/0/prometheus/vmalert/
VMAlert - executes a list of given alerting or recording rules against configured address.
The VMAlert CRD declaratively defines a desired VMAlert setup to run in a Kubernetes cluster.
It has few required config options - datasource and notifier are required, for other config parameters check doc.
For each VMAlert resource, the Operator deploys a properly configured Deployment in the same namespace. The VMAlert Pods are configured to mount a list of Configmaps prefixed with <VMAlert-name>-number containing the configuration for alerting rules.
URL: https://alertmanager.cmn.SYSTEM_DOMAIN_NAME/
Central Alertmanager instance that manages Prometheus alerts.
The Alertmanager manages the alerts it receives and generates notifications to users or applications. For more information about alert-manager, see
Getting Started/ in the Prometheus online documentation.
Some alerts may be falsely triggered. This occurs if they are alerts which will be improved in the future, or if they are alerts impacted by whether all software products have been installed yet. See Troubleshoot Prometheus Alerts.
URL: https://grafana.cmn.SYSTEM_DOMAIN_NAME/
Central Grafana instance that includes numerous dashboards for visualizing metrics from prometheus and prometheus-istio.
For more information, see the Grafana online documentation:
URL: https://kiali-istio.cmn.SYSTEM_DOMAIN_NAME/
Kiali provides real-time introspection into the Istio service mesh using metrics and traces from Istio.
For more information about the features of this interface, refer to the Kiali online documentation/.