https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/Recent content in Kube-Prometheus on Prometheus OperatorHugo -- gohugo.ioen-USTue, 06 Oct 2020 08:48:23 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/access-ui/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/access-ui/Prometheus, Grafana, and Alertmanager dashboards can be accessed quickly using kubectl port-forward after running the quickstart via the commands below. Kubernetes 1.10 or later is required. You can also learn how to expose Prometheus/Alertmanager/Grafana via Ingress Prometheus # kubectl --namespace monitoring port-forward svc/prometheus-k8s 9090 Open Prometheus on http://localhost:9090 in your browser. Check out the alerts and rules pages with the pre-configured rules and alerts! This Prometheus is supposed to monitor your Kubernetes cluster and make sure to alert you if there’s a problem with it.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/deploy-kind/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/deploy-kind/Time to explain how! Your chance of contributing!https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/kube-prometheus-on-kubeadm/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/kube-prometheus-on-kubeadm/The kubeadm tool is linked by Kubernetes as the offical way to deploy and manage self-hosted clusters. kubeadm does a lot of heavy lifting by automatically configuring your Kubernetes cluster with some common options. This guide is intended to show you how to deploy Prometheus, Prometheus Operator and Kube Prometheus to get you started monitoring your cluster that was deployed with kubeadm. This guide assumes you have a basic understanding of how to use the functionality the Prometheus Operator implements.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/exposing-prometheus-alertmanager-grafana-ingress/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/exposing-prometheus-alertmanager-grafana-ingress/In order to access the web interfaces via the Internet Kubernetes Ingress is a popular option. This guide explains, how Kubernetes Ingress can be setup, in order to expose the Prometheus, Alertmanager and Grafana UIs, that are included in the kube-prometheus project. Note: before continuing, it is recommended to first get familiar with the kube-prometheus stack by itself. Prerequisites # Apart from a running Kubernetes cluster with a running kube-prometheus stack, a Kubernetes Ingress controller must be installed and functional.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/blackbox-exporter/Mon, 08 Mar 2021 08:49:31 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/blackbox-exporter/Setting up a blackbox exporter # The prometheus-operator defines a Probe resource type that can be used to describe blackbox checks. To execute these, a separate component called blackbox_exporter has to be deployed, which can be scraped to retrieve the results of these checks. You can use kube-prometheus to set up such a blackbox exporter within your Kubernetes cluster. Adding blackbox exporter manifests to an existing kube-prometheus configuration # Override blackbox-related configuration parameters as needed.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/monitoring-external-etcd/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/monitoring-external-etcd/When the etcd cluster is not hosted inside Kubernetes. This is often the case with Kubernetes setups. This approach has been tested with kube-aws but the same principals apply to other tools. Note that etcd.jsonnet & static-etcd.libsonnet (which are described by a section of the customization) do the following: Put the three etcd TLS client files (CA & cert & key) into a secret in the namespace, and have Prometheus Operator load the secret.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/monitoring-other-namespaces/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/monitoring-other-namespaces/By default the RBAC rules are only enabled for the Default and kube-system namespaces. Setup # You have to give the list of the namespaces that you want to be able to monitor. This is done in the variable prometheus.roleSpecificNamespaces. You usually set this in your .jsonnet file when building the manifests. Example to create the needed Role and RoleBinding for the Namespace foo : local kp = (import 'kube-prometheus/main.libsonnet') + { values+:: { common+: { namespace: 'monitoring', }, prometheus+:: { namespaces: ["default", "kube-system", "monitoring", "foo"], }, }, }; { 'setup/0namespace-namespace': kp.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/developing-prometheus-rules-and-grafana-dashboards/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/kube-prometheus/kube/developing-prometheus-rules-and-grafana-dashboards/kube-prometheus ships with a set of default Prometheus rules and Grafana dashboards. At some point one might like to extend them, the purpose of this document is to explain how to do this. All manifests of kube-prometheus are generated using jsonnet. Prometheus rules and Grafana dashboards in specific follow the Prometheus Monitoring Mixins proposal. For both the Prometheus rules and the Grafana dashboards Kubernetes ConfigMaps are generated within kube-prometheus. In order to add additional rules and dashboards simply merge them onto the existing json objects.