Prometheus, Grafana, and Alertmanager
Use Prometheus, Grafana, and Alertmanager when you deploy the CDM.
After you’ve finished deploying the CDM, you can use the CDM as a sandbox to explore deployment with a different monitoring and alerting framework.
Remember, the CDM is a reference implementation and not for production use. When you create a project plan, you’ll need to determine how to monitor and send alerts in your production deployment.
To deploy Prometheus, Grafana, and Alertmanager:
Deploy Prometheus, Grafana, and Alertmanager in your cluster. You can safely ignore
info: skipping unknown hook: "crd-install"messages:
$ /path/to/forgeops/bin/prometheus-deploy.sh This script requires Helm version 3.04 or later due to changes in the behaviour of 'helm repo add' command. namespace/monitoring created "stable" has been added to your repositories "prometheus-community" has been added to your repositories Hang tight while we grab the latest from your chart repositories… …Successfully got an update from the "ingress-nginx" chart repository …Successfully got an update from the "codecentric" chart repository …Successfully got an update from the "prometheus-community" chart repository …Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Release "prometheus-operator" does not exist. Installing it now. NAME: prometheus-operator LAST DEPLOYED: Mon May 10 14:28:42 2021 NAMESPACE: monitoring STATUS: deployed REVISION: 1 NOTES: kube-prometheus-stack has been installed. Check its status by running: kubectl --namespace monitoring get pods -l "release=prometheus-operator" Visit https://github.com/prometheus-operator/kube-prometheus for instructions on how to create & configure Alertmanager and Prometheus instances using the Operator. . . . Release "forgerock-metrics" does not exist. Installing it now. NAME: forgerock-metrics LAST DEPLOYED: Mon May 10 14:29:57 2021 NAMESPACE: monitoring STATUS: deployed REVISION: 1 TEST SUITE: None
Check the status of the pods in the
monitoringnamespace until all the pods are ready:
$ kubectl get pods --namespace monitoring NAME READY STATUS RESTARTS AGE alertmanager-prometheus-operator-kube-p-alertmanager-0 2/2 Running 0 2m49s prometheus-operator-grafana-7fb6687584-g7mll 2/2 Running 0 2m55s prometheus-operator-kube-p-operator-648f6dc47f-qsdkl 1/1 Running 0 2m55s prometheus-operator-kube-state-metrics-957fc5f95-jwvdz 1/1 Running 0 2m55s prometheus-operator-prometheus-node-exporter-dd4vz 1/1 Running 0 2m55s prometheus-operator-prometheus-node-exporter-dtblt 1/1 Running 0 2m56s prometheus-operator-prometheus-node-exporter-jvlj5 1/1 Running 0 2m55s prometheus-prometheus-operator-kube-p-prometheus-0 2/2 Running 1 2m49s