It configures Prometheus, Grafana, Alertmanager, and vital metrics exporters for you, reducing maintenance overheads. Kube-Prometheus-Stack is a convenient route to setting up monitoring for your cluster. You need to understand resource utilization, see where Pods are being scheduled, and track the errors and logs emitted by your applications. Good observability is essential for Kubernetes clusters running production workloads. Kube-Prometheus-Stack provides an automated solution that performs all the hard work for you. You can use it to get an email when CPU utilization spikes or a Slack notification if a Pod is evicted, for example.ĭeploying, configuring, and maintaining all these components individually can be burdensome for administrators. Alertmanager – Alertmanager is a standalone Prometheus component that provides notifications when metrics change.You can use it to create dashboards that surface your Prometheus data. Grafana is an observability platform that works with several data sources, including Prometheus databases. Grafana – Although you can directly query Prometheus, this is often tedious and repetitive.It exposes information about the API objects in your Kubernetes cluster, such as Pods and containers. Kube-State-Metrics – Kube-State-Metrics is another exporter that supplies data to Prometheus.The kube-prometheus-stack chart automatically deploys this exporter and configures your Prometheus instance to scrape it. Node-Exporter is an exporter which collects resource utilization data from the Nodes in your Kubernetes cluster. Node-Exporter – Prometheus works by scraping data from a variety of configurable sources called exporters.Prometheus – Prometheus is the time series database that scrapes, stores, and exposes the metrics from your Kubernetes environment and its applications.It bundles several different components in one automated deployment: Get KubeSphere v3.0.0 customized kube-prometheus.The kube-prometheus-stack Helm chart is the simplest way to bring up a complete Prometheus stack inside your Kubernetes cluster. You must copy the recording/alerting rules in PrometheusRule and PrometheusRule for ETCD to your Prometheus config for KubeSphere v3.0.0 to work properly.Ĭonfigure your Prometheus to scrape metrics from the same targets as the ServiceMonitors listed in KubeSphere kustomization. If your Prometheus stack setup isn’t managed by Prometheus Operator, you can skip this step. You can remove xxx-serviceMonitor.yaml if you don’t want your own ServiceMonitors to be overwritten (KubeSphere customized ServiceMonitors discard many irrelevant metrics to make sure Prometheus only stores the most useful metrics). You can remove alertmanager-secret.yaml if you don’t want your existing Alertmanager’s config to be overwritten. There are a few items listed in KubeSphere kustomization, among which prometheus-rules.yaml and prometheus-rulesEtcd.yaml are required for KubeSphere v3.0.0 to work properly and others are optional. KubeSphere 3.0.0 uses Prometheus Operator to manage Prometheus/Alertmanager config and lifecycle, ServiceMonitor (to manage scrape config), and PrometheusRule (to manage Prometheus recording/alert rules). Kubectl -n kubesphere-system exec $(kubectl get pod -n kubesphere-system -l app =ks-install -o jsonpath = '') - kubectl delete -f /kubesphere/kubesphere/prometheus/init/ 2>/dev/null
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |