微服务监控神器Prometheus的安装部署
本文涉及：如何在k8s下搭建Prometheus+grafana的监控环境
基本概念
Prometheus提供了容器和云原生领域数据搜集、存储、处理、可视化和告警一套完整的解决方案，最初时是由SoundCloud公司开发的。自2012年开源以来社区成员就不断递增。如今的Prometheus已经发展到继Kubernetes后第2个正式加入CNCF基金会的项目
Prometheus的特点？
- 多维的数据模型（基于时间序列的k/v键值对）。
- 灵活的查询及聚合语句（PromQL）。
- 不依赖分布式存储，节点自治。
- 基于HTTP的pull模式采集时间序列数据。
- 可以使用pushgateway（prometheus的可选中间件）实现push模式。
- 可以使用动态服务发现或静态配置采集的目标机器。
- 支持多种图形及仪表盘。
Prometheus可以监控什么？
k8s、docker、mysql、redis、es、consul、rabbitmq、zabbix等等
Prometheus架构图
Prometheus安装部署
Helm 安装
Helm 是一个命令行下的客户端工具。主要用于 Kubernetes 应用程序 Chart 的创建、打包、发布以及创建和管理本地和远程的 Chart 仓库。
[root@syj ~]# wget https://storage.googleapis.com/kubernetes-helm/helm-v2.13.1-rc.2-linux-amd64.tar.gz[root@syj ~]# tar -zxvf helm-v2.14.0-rc.2-linux-amd64.tar.gz[root@syj ~]# cp linux-amd64/helm /usr/local/bin/[root@syj ~]# helm versionClient: &version.Version{SemVer:"v2.13.1-rc.2", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}Error: could not find tillerTiller 服务器安装
Tiller 是 Helm 的服务端，部署在 Kubernetes 集群中。Tiller 用于接收 Helm 的请求，并根据 Chart 生成 Kubernetes 的部署文件（ Helm 称为 Release ），然后提交给 Kubernetes 创建应用。Tiller 还提供了 Release 的升级、删除、回滚等一系列功能。
创建rbac-config.yaml
apiVersion: v1kind: ServiceAccountmetadata: name: tiller namespace: kube-system---apiVersion: rbac.authorization.k8s.io/v1kind: ClusterRoleBindingmetadata: name: tillerroleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-adminsubjects: - kind: ServiceAccount name: tiller namespace: kube-system启动
[root@syj ~]# kubectl apply -f rbac-config.yaml serviceaccount/tiller createdclusterrolebinding.rbac.authorization.k8s.io/tiller created使用阿里云镜像进行安装
[root@syj ~]# helm init --service-account tiller --upgrade -i registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.13.1 --stable-repo-url https://kubernetes.oss-cn-hangzhou.aliyuncs.com/charts
Creating /root/.helmCreating /root/.helm/repositoryCreating /root/.helm/repository/cacheCreating /root/.helm/repository/localCreating /root/.helm/pluginsCreating /root/.helm/startersCreating /root/.helm/cache/archiveCreating /root/.helm/repository/repositories.yamlAdding stable repo with URL: https://kubernetes.oss-cn-hangzhou.aliyuncs.com/chartsAdding local repo with URL: http://127.0.0.1:8879/charts$HELM_HOME has been configured at /root/.helm.Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.To prevent this, run `helm init` with the --tiller-tls-verify flag.For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installationHappy Helming!查看结果
[root@syj ~]# helm versionClient: &version.Version{SemVer:"v2.13.1", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}Server: &version.Version{SemVer:"v2.13.1", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}[root@syj ~]# helm repo listNAME URL stable https://kubernetes.oss-cn-hangzhou.aliyuncs.com/chartslocal http://127.0.0.1:8879/charts部署 Prometheus Operator
创建命名空间
[root@syj ~]# kubectl create namespace monitoring下载Prometheus Operator
[root@syj ~]# wget https://github.com/coreos/prometheus-operator/archive/release-0.29.zip将下载下来的依赖包解压并重命名为prometheus-operator并cd到此目录
安装prometheus相关内容
helm install --name prometheus-operator --set rbacEnable=true --namespace=monitoring helm/prometheus-operatorhelm install --name prometheus --set serviceMonitorsSelector.app=prometheus --set ruleSelector.app=prometheus --namespace=monitoring helm/prometheushelm install --name alertmanager --namespace=monitoring helm/alertmanager验证
[root@syj ~]# kubectl get pod -n monitoringNAME READY STATUS RESTARTS AGEalertmanager-alertmanager-0 2/2 Running 0 58sprometheus-operator-545b59ffc9-6g7dg 1/1 Running 0 6m32sprometheus-prometheus-0 3/3 Running 1 3m31s[root@syj ~]# kubectl get svc -n monitoringNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEalertmanager ClusterIP 10.98.237.7 <none> 9093/TCP 87salertmanager-operated ClusterIP None <none> 9093/TCP,6783/TCP 87sprometheus ClusterIP 10.104.185.104 <none> 9090/TCP 4mprometheus-operated ClusterIP None <none> 9090/TCP 4m安装 kube-prometheus
[root@syj ~]# mkdir -p helm/kube-prometheus/charts[root@syj ~]# helm package -d helm/kube-prometheus/charts helm/alertmanager helm/grafana helm/prometheus helm/exporter-kube-dns \> helm/exporter-kube-scheduler helm/exporter-kubelets helm/exporter-node helm/exporter-kube-controller-manager \> helm/exporter-kube-etcd helm/exporter-kube-state helm/exporter-coredns helm/exporter-kubernetes验证
[root@syj ~]# kubectl get svc -n monitoringNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEalertmanager ClusterIP 10.98.237.7 <none> 9093/TCP 34malertmanager-operated ClusterIP None <none> 9093/TCP,6783/TCP 34mkube-prometheus ClusterIP 10.101.249.82 <none> 9090/TCP 29skube-prometheus-alertmanager ClusterIP 10.100.29.63 <none> 9093/TCP 29skube-prometheus-exporter-kube-state ClusterIP 10.98.91.146 <none> 80/TCP 29skube-prometheus-exporter-node ClusterIP 10.98.34.11 <none> 9100/TCP 29skube-prometheus-grafana ClusterIP 10.108.208.247 <none> 80/TCP 29sprometheus ClusterIP 10.104.185.104 <none> 9090/TCP 36mprometheus-operated ClusterIP None <none> 9090/TCP 36m将grafana的Service类型改为NodePort
kubectl patch svc kube-prometheus-grafana -p '{"spec":{"type":"NodePort"}}' -n monitoring此时访问grafana的默认端口31106即可：
http://ip:31106安装过程参考文章：https://blog.csdn.net/wangzan18/article/details/85270816
grafana的各种模板可参考
https://grafana.com/dashboards
本文参与 腾讯云自媒体分享计划，分享自微信公众号。
原始发表：2019-05-20，如有侵权请联系 cloudcommunity@tencent.com 删除
评论
登录后参与评论
推荐阅读