wordpress项目管理插件,网站关键词优化排名外包,云南中建西部建设有限公司网站,网站建设微分销一、基于文件的服务发现
基于文件的服务发现是仅仅略优于静态配置的服务发现方式#xff0c;它不依赖于任何平台或第三方服务#xff0c;因而也是最为简单和通用的实现方式。 Prometheus Server 会定期从文件中加载 Target 信息#xff0c;文件可使用 YAML 和 JSON 格式它不依赖于任何平台或第三方服务因而也是最为简单和通用的实现方式。 Prometheus Server 会定期从文件中加载 Target 信息文件可使用 YAML 和 JSON 格式它含有定义的 Target 列表以及可选的标签信息。 创建用于服务发现的文件在文件中配置所需的 target
cd /usr/local/prometheus
mkdir file_sd
cd file_sd/
vim node-exporter.yaml
- targets:- 192.168.10.30:9100labels:svc: node vim prometheus.yml
- job_name: node_exporterscheme: httpmetrics_path: /metricsfile_sd_configs: #指定使用文件服务发现- files: #指定要加载的文件列表- file_sd/node-exporter.yaml #文件加载
systemctl restart prometheus.service 通过修改配置文件 node-exporter.yaml可以设置监控的主机节点 二、基于 Consul 的服务发现
Consul 是一款基于 golang 开发的开源工具主要面向分布式服务化的系统提供服务注册、服务发现和配置管理的功能。 提供服务注册/发现、健康检查、Key/Value存储、多数据中心和分布式一致性保证等功能。
下载地址https://www.consul.io/downloads/
cd /opt
上传consul_1.9.2_linux_amd64.zip
unzip consul_1.9.2_linux_amd64.zip
mv consul /usr/local/bin/
consul version cd /usr/local/
mkdir consul
cd consul/
mkdir data conf logs
consul agent \-server \-bootstrap \-ui \-data-dir/usr/local/consul/data \-config-dir/usr/local/consul/conf \-bind192.168.10.31 \-client0.0.0.0 \-nodeconsul-server01 /usr/local/consul/logs/consul.log netstat -lntp | grep consul 使用consul发现目标主机 cd /usr/local/consul/conf
vim nodes.json
{services: [{id: node_exporter-node01,name: node01,address: 192.168.10.31,port: 9100,tags: [nodes],checks: [{http: http://192.168.10.31:9100/metrics,interval: 5s}]},{id: node_exporter-node02,name: node01,address: 192.168.10.30,port: 9100,tags: [nodes],checks: [{http: http://192.168.10.30:9100/metrics,interval: 5s}]}]
}consul reload 关联普罗米修斯
vim prometheus.yml- job_name: node_exporterscheme: httpmetrics_path: /metricsconsul_sd_configs:- server: 192.168.10.31:8500tags:- nodesrefresh_interval: 1m 每隔1分钟重新加载一次文件中定义的 Targets默认为 5m
systemctl restart prometheus.service 如何剔除/添加consul中的主机
consul services deregister -id node_exporter-node01consul services register ./nodes.json 三、基于 Kubernetes API 的服务发现
基于 Kubernetes API 的服务发现机制支持将 API Server 中 Node、Service、Endpoint、Pod 和 Ingress 等资源类型下相应的各资源对象视作 target 并持续监视相关资源的变动
●Node、Service、Endpoint、Pod 和 Ingress 资源分别由各自的发现机制进行定义
●负责发现每种类型资源对象的组件在 Prometheus 中称为一个 role
●支持在集群上基于 DaemonSet 控制器部署 node-exporter 后发现各 Node 节点也可以通过 kubelet 来作为 Prometheus 发现各 Node 节点的入口
k8s主节点操作vim rbac.yaml
apiVersion: v1
kind: Namespace
metadata:name: monitoring---
apiVersion: v1
kind: ServiceAccount
metadata:name: outside-prometheusnamespace: monitoring---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:name: outside-prometheus
rules:
- apiGroups:- resources:- nodes- services- endpoints- pods- nodes/proxyverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingressesverbs:- get- list- watch
- apiGroups:- resources:- configmaps- nodes/metricsverbs:- get
- nonResourceURLs:- /metricsverbs:- get---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:name: outside-prometheus
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: outside-prometheus
subjects:
- kind: ServiceAccountname: outside-prometheusnamespace: monitoring
kubectl apply -f rbac.yaml获取ServiceAccount对应Secret资源对象中保存的token然后将token保存到Prometheus节点上的文件里。TOKENkubectl get secret/$(kubectl -n monitoring get secret | awk /outside-prometheus/{print $1}) -n monitoring -o jsonpath{.data.token} | base64 -decho $TOKENcd /etc/kubernetes/pki/
scp ca.crt 192.168.10.31:/usr/local/prometheus
prometheus服务器
cd /usr/local/prometheus
echo eyJhbGciOiJSUzI1NiIsImtpZCI6IlVlekNjZThYQ1lGNHVUVzFkeXdVbjhtaGUzbFJuMzZSeXV4VWExMnJVUzAifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJtb25pdG9yaW5nIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6Im91dHNpZGUtcHJvbWV0aGV1cy10b2tlbi12OGJtOSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJvdXRzaWRlLXByb21ldGhldXMiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJmYWEwNjA1NC0zZWRhLTQ2MmQtODE0NS0yNjYzYTU0ZTM3MmIiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6bW9uaXRvcmluZzpvdXRzaWRlLXByb21ldGhldXMifQ.jzBcGYgiADGQ1MxR-9xJ7dCIAFI2aCkuX64w6AzDDIwV_XMRUNNSIoX6867Mu3ebuFPChBX6B0bIJ-SrxspjSNIOBiuYSuCKXNqwwxfpVSNNq_v40JFBxn7NpzxrLDHm5eq8scwWMEy6HPVdN83uhU4Zrd4GVenArirwKScsl_bphjrFf-vp1Z9aMWH241BzJtvv-aQ2m0-dQ13ZljZ-YP_FO-lz0EGuECfyiIozFkDPwooMowRxy68m0liwGo-McrKttv3BC8KJcSmSmFZyGAzQuNoHa8j5FIOHMJxlhfIxXlrTDSUEUgBSjsOWMKXEN_mMBzi4lLHIwfMJDv4Zmw k8s-api-token
cat k8s-api-token
k8s主节点
kubectl create clusterrolebinding cluster-system-anonymous --clusterrolecluster-admin --usersystem:anonymous
prometheus服务器
vim prometheus.yml
- job_name: k8s-apiserverscheme: httpskubernetes_sd_configs:- role: endpointsapi_server: https://192.168.10.30:6443tls_config:ca_file: /usr/local/prometheus/ca.crtauthorization:credentials_file: /usr/local/prometheus/k8s-api-tokentls_config:ca_file: /usr/local/prometheus/ca.crtauthorization:credentials_file: /usr/local/prometheus/k8s-api-tokenrelabel_configs:- source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_endpoints_name, __meta_kubernetes_endpoint_port_name]regex: default;kubernetes;httpsaction: keep- job_name: kubernetes-nodeskubernetes_sd_configs:- role: nodeapi_server: https://192.168.10.30:6443tls_config:ca_file: /usr/local/prometheus/ca.crtauthorization:credentials_file: /usr/local/prometheus/k8s-api-tokenrelabel_configs:- source_labels: [__address__]regex: (.*):10250action: replacetarget_label: __address__replacement: $1:9100- action: labelmapregex: __meta_kubernetes_node_label_(.)systemctl restart prometheus.service
