当前位置: 首页 > news >正文

做网站发布微商引流被加方法精准客源

做网站发布,微商引流被加方法精准客源,漳州网站建设到博大,活动策划书模板本节重点介绍 : push模型和pull模型监控系统对比为什么在k8s中只能用pull模型的k8s中主要组件的暴露地址说明 push模型和pull模型监控系统 对比下两种系统采用的不同采集模型,即push型采集和pull型采集。不同的模型在性能的考虑上是截然不同的。下面表格简单的说…

本节重点介绍 :

  • push模型和pull模型监控系统对比
  • 为什么在k8s中只能用pull模型的
  • k8s中主要组件的暴露地址说明

push模型和pull模型监控系统

  • 对比下两种系统采用的不同采集模型,即push型采集和pull型采集。不同的模型在性能的考虑上是截然不同的。下面表格简单的说明了下两种模型的特点:
采集模型原理简介代表
pushagent定时推送数据到server夜莺&open-falcon
pullserver定时去agent拉数据prometheus

就采集器是否丰富来说

  • 我们需要对比的是这个系统是否有很好的插件扩展机制,因为这直接决定了开源社区对该系统采集器贡献的活跃度
  • prometheus采集的pull模型,使用者可以用自定义exporter的模式灵活的接入。

push型的致命缺点 agent和服务端强耦合

  • 那就是agent需要配置服务端地址,带来了一定的耦合性,不适合云原生场景。
  • 如果采用push型,试想一下你的应用部署在k8s中,在启动的时候需要指定监控上报的服务地址,那是不能接受的。
  • 类比pushgateway的例子pusher = push.New(url, jobName) 必须要指定服务端的地址

如果push端的服务地址变化了怎么办

  • 一个典型的场景就是在k8s中,pod的扩缩十分频繁,服务端的地址也不固定。

pull型的处理方法

  • 对比来说,应用pull模型采集的prometheus,可以对接多种服务发现源,特别适合k8s环境。
  • 举个例子,应用的pod一旦发生变化,prometheus就可以通过配置好k8s的服务发现模式监听到资源变化,进行采集的增删,agent侧只需要暴露自己的指标,完全不关心是哪一个server过来获取数据。

k8s中主要组件的暴露地址说明

部署在pod中业务埋点指标

  • 是直接通过pod的ip暴露的,我们可以直接通过get pod 获取容器的ip,在node上直接curl访问到
[root@k8s-master01 ink8s-pod-metrics]# kubectl get pod -o wide                
NAME                                           READY   STATUS    RESTARTS   AGE     IP              NODE         NOMINATED NODE   READINESS GATES
ink8s-pod-metrics-deployment-85d9795d6-95lsp   1/1     Running   0          13h     10.100.85.207   k8s-node01   <none>           <none>
[root@k8s-master01 ink8s-pod-metrics]# curl -s 10.100.85.207:8080/metrics |grep ink8s                               # HELP ink8s_pod_metrics_get_node_detail k8s node detail each
# TYPE ink8s_pod_metrics_get_node_detail gauge
ink8s_pod_metrics_get_node_detail{containerRuntimeVersion="containerd://1.4.4",hostname="k8s-master01",ip="172.20.70.205",kubeletVersion="v1.20.1"} 1
ink8s_pod_metrics_get_node_detail{containerRuntimeVersion="containerd://1.4.4",hostname="k8s-node01",ip="172.20.70.215",kubeletVersion="v1.20.1"} 1
# HELP ink8s_pod_metrics_get_node_last_duration_seconds get node last duration seconds
# TYPE ink8s_pod_metrics_get_node_last_duration_seconds gauge
ink8s_pod_metrics_get_node_last_duration_seconds 0.008506914
# HELP ink8s_pod_metrics_get_pod_control_plane_pod_detail k8s pod detail of control plane
# TYPE ink8s_pod_metrics_get_pod_control_plane_pod_detail gauge
ink8s_pod_metrics_get_pod_control_plane_pod_detail{component="etcd",ip="172.20.70.205",pod_name="etcd-k8s-master01"} 1
ink8s_pod_metrics_get_pod_control_plane_pod_detail{component="kube-apiserver",ip="172.20.70.205",pod_name="kube-apiserver-k8s-master01"} 1
ink8s_pod_metrics_get_pod_control_plane_pod_detail{component="kube-controller-manager",ip="172.20.70.205",pod_name="kube-controller-manager-k8s-master01"} 1
ink8s_pod_metrics_get_pod_control_plane_pod_detail{component="kube-scheduler",ip="172.20.70.205",pod_name="kube-scheduler-k8s-master01"} 1
# HELP ink8s_pod_metrics_get_pod_last_duration_seconds get pod last duration seconds
# TYPE ink8s_pod_metrics_get_pod_last_duration_seconds gauge
ink8s_pod_metrics_get_pod_last_duration_seconds 0.012481561
  • target页面举例图片
  • image.png

容器基础资源指标

  • kubelet 内置cadvisor metrics接口暴露的
  • 我们可以先获取token,再使用token作为header访问各个节点的cadvisor指标
TOKEN=$(kubectl -n kube-system  get secret $(kubectl -n kube-system  get serviceaccount prometheus -o jsonpath='{.secrets[0].name}') -o jsonpath='{.data.token}' | base64 --decode )
curl -s   https://172.20.70.215:10250/metrics/cadvisor --header "Authorization: Bearer $TOKEN" --insecure  |head  # HELP cadvisor_version_info A metric with a constant '1' value labeled by kernel version, OS version, docker version, cadvisor version & cadvisor revision.
# TYPE cadvisor_version_info gauge
cadvisor_version_info{cadvisorRevision="",cadvisorVersion="",dockerVersion="1.13.1",kernelVersion="3.10.0-957.1.3.el7.x86_64",osVersion="CentOS Linux 7 (Core)"} 1
# HELP container_cpu_cfs_periods_total Number of elapsed enforcement period intervals.
# TYPE container_cpu_cfs_periods_total counter
container_cpu_cfs_periods_total{container="",id="/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod6ab97c68_b0ac_48ce_ba39_6ffa72a2f4c8.slice",image="",name="",namespace="default",pod="ink8s-pod-metrics-deployment-85d9795d6-95lsp"} 46664 1629771810858
container_cpu_cfs_periods_total{container="",id="/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podbf3f353a_92fa_4436_a8ca_6cb632d48ada.slice",image="",name="",namespace="kube-admin",pod="k8s-mon-daemonset-z6sfw"} 762965 1629771819606
container_cpu_cfs_periods_total{container="",id="/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podd9a95d67_a843_4369_8d5c_34a5333f1480.slice",image="",name="",namespace="kube-admin",pod="k8s-mon-deployment-6d7d58bdc8-rxj42"} 458822 1629771809776
container_cpu_cfs_periods_total{container="",id="/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode27c9fe7_9d82_4228_86fb_b9c920611c15.slice",image="",name="",namespace="kube-system",pod="prometheus-0"} 941374 1629771809770
container_cpu_cfs_periods_total{container="ink8s-pod-metrics",id="/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod6ab97c68_b0ac_48ce_ba39_6ffa72a2f4c8.slice/cri-containerd-2f85fd45a67cc4bb775b99d4676200b412ea18ef7ae4976fc93a8a7cff1c5f34.scope",image="docker.io/library/ink8s-pod-metrics:v1",name="2f85fd45a67cc4bb775b99d4676200b412ea18ef7ae4976fc93a8a7cff1c5f34",namespace="default",pod="ink8s-pod-metrics-deployment-85d9795d6-95lsp"} 46667 1629771818053
  • target页面举例图片
  • image.png

k8s对象资源指标

  • 这是ksm直接暴露指标,prometheus通过dns解析到域名然后访问的
  • 我们可以通过dig获取ksm 的service_ip,然后访问 service_ip:8080
 dig +short kube-state-metrics.kube-system.svc.cluster.local @10.96.0.10
10.100.85.200
curl -s 10.100.85.200:8080/metrics  |head  # HELP kube_certificatesigningrequest_labels Kubernetes labels converted to Prometheus labels.
# TYPE kube_certificatesigningrequest_labels gauge
# HELP kube_certificatesigningrequest_created Unix creation timestamp
# TYPE kube_certificatesigningrequest_created gauge
# HELP kube_certificatesigningrequest_condition The number of each certificatesigningrequest condition
# TYPE kube_certificatesigningrequest_condition gauge
# HELP kube_certificatesigningrequest_cert_length Length of the issued cert
# TYPE kube_certificatesigningrequest_cert_length gauge
# HELP kube_configmap_info Information about configmap.
# TYPE kube_configmap_info gauge
  • target页面举例图片
  • image.png

k8s服务组件指标

  • 是由服务组件自身直接暴露的,我们也可以通过带token直接访问
TOKEN=$(kubectl -n kube-system  get secret $(kubectl -n kube-system  get serviceaccount prometheus -o jsonpath='{.secrets[0].name}') -o jsonpath='{.data.token}' | base64 --decode )
curl -s  https://localhost:6443/metrics --header "Authorization: Bearer $TOKEN" --insecure |head  # HELP aggregator_openapi_v2_regeneration_count [ALPHA] Counter of OpenAPI v2 spec regeneration count broken down by causing APIService name and reason.
# TYPE aggregator_openapi_v2_regeneration_count counter
aggregator_openapi_v2_regeneration_count{apiservice="*",reason="startup"} 0
aggregator_openapi_v2_regeneration_count{apiservice="k8s_internal_local_delegation_chain_0000000002",reason="update"} 0
# HELP aggregator_openapi_v2_regeneration_duration [ALPHA] Gauge of OpenAPI v2 spec regeneration duration in seconds.
# TYPE aggregator_openapi_v2_regeneration_duration gauge
aggregator_openapi_v2_regeneration_duration{reason="startup"} 0.812717406
aggregator_openapi_v2_regeneration_duration{reason="update"} 0.848521427
# HELP aggregator_unavailable_apiservice [ALPHA] Gauge of APIServices which are marked as unavailable broken down by APIService name.
# TYPE aggregator_unavailable_apiservice gauge
[root@k8s-master01 ink8s-pod-metrics]# 
  • target页面举例图片
  • image.png

k8s中关注四大块指标总结

  • 之前在k8s中关注4块指标有过总结
指标类型采集源应用举例发现类型
容器基础资源指标kubelet 内置cadvisor metrics接口查看容器cpu、mem利用率等k8s_sd node级别直接访问node_ip
k8s对象资源指标kube-stats-metrics (简称ksm)具体可以看 <br> 看pod状态如pod waiting状态的原因 <br> 数个数如:查看node pod按namespace分布情况通过coredns访问域名
k8s服务组件指标服务组件 metrics接口查看apiserver 、scheduler、etc、coredns请求延迟等k8s_sd endpoint级别
部署在pod中业务埋点指标pod 的metrics接口依据业务指标场景k8s_sd pod级别,访问pod ip的metricspath

本节重点总结 :

  • push模型和pull模型监控系统对比
  • 为什么在k8s中只能用pull模型的
  • k8s中主要组件的暴露地址说明

文章转载自:
http://dinncoepitaph.zfyr.cn
http://dinncoparchment.zfyr.cn
http://dinncointercessory.zfyr.cn
http://dinncoshorthand.zfyr.cn
http://dinncoplanarian.zfyr.cn
http://dinncobegum.zfyr.cn
http://dinncofootbinding.zfyr.cn
http://dinncoalgesimeter.zfyr.cn
http://dinncounderbite.zfyr.cn
http://dinncoscrambler.zfyr.cn
http://dinncohelleri.zfyr.cn
http://dinncovum.zfyr.cn
http://dinncodiscodance.zfyr.cn
http://dinncochiseler.zfyr.cn
http://dinncoballute.zfyr.cn
http://dinncotercet.zfyr.cn
http://dinncocoaxingly.zfyr.cn
http://dinncoacronichal.zfyr.cn
http://dinncorapper.zfyr.cn
http://dinncojohns.zfyr.cn
http://dinncohyson.zfyr.cn
http://dinncohippophobia.zfyr.cn
http://dinncounpersuasive.zfyr.cn
http://dinncometasomatosis.zfyr.cn
http://dinncobiowarfare.zfyr.cn
http://dinncodecode.zfyr.cn
http://dinncoturbosupercharged.zfyr.cn
http://dinncomaskinonge.zfyr.cn
http://dinncoquamash.zfyr.cn
http://dinncozinckenite.zfyr.cn
http://dinncocomplaint.zfyr.cn
http://dinncoionisation.zfyr.cn
http://dinncophantasmatic.zfyr.cn
http://dinncosawblade.zfyr.cn
http://dinncomonkeyshine.zfyr.cn
http://dinncoinformality.zfyr.cn
http://dinncosextillion.zfyr.cn
http://dinncogawky.zfyr.cn
http://dinncostylet.zfyr.cn
http://dinncodeletion.zfyr.cn
http://dinncobivalence.zfyr.cn
http://dinncoshlump.zfyr.cn
http://dinncouranus.zfyr.cn
http://dinncoroo.zfyr.cn
http://dinncomonoblastic.zfyr.cn
http://dinncoconquer.zfyr.cn
http://dinncoskullfish.zfyr.cn
http://dinncobody.zfyr.cn
http://dinncomonticle.zfyr.cn
http://dinncoacetylco.zfyr.cn
http://dinncodisaffinity.zfyr.cn
http://dinncoepsomite.zfyr.cn
http://dinncowherewith.zfyr.cn
http://dinncoleave.zfyr.cn
http://dinncoqmg.zfyr.cn
http://dinncoconsonantal.zfyr.cn
http://dinncodingbat.zfyr.cn
http://dinncopsychosomatic.zfyr.cn
http://dinncobloated.zfyr.cn
http://dinncomerrily.zfyr.cn
http://dinncopatricia.zfyr.cn
http://dinncophloxin.zfyr.cn
http://dinncounintermitted.zfyr.cn
http://dinncoexceptious.zfyr.cn
http://dinncoheldentenor.zfyr.cn
http://dinncosense.zfyr.cn
http://dinncoerotism.zfyr.cn
http://dinncoweld.zfyr.cn
http://dinncozedoary.zfyr.cn
http://dinncopiny.zfyr.cn
http://dinncobalneology.zfyr.cn
http://dinncogrommet.zfyr.cn
http://dinncosearch.zfyr.cn
http://dinncoackey.zfyr.cn
http://dinncovicissitudinous.zfyr.cn
http://dinncohydrotropic.zfyr.cn
http://dinncogaudiness.zfyr.cn
http://dinncotheopathetic.zfyr.cn
http://dinncophidippides.zfyr.cn
http://dinncoanatomize.zfyr.cn
http://dinncosexless.zfyr.cn
http://dinncoaggrandizement.zfyr.cn
http://dinncogsdi.zfyr.cn
http://dinncobrunswick.zfyr.cn
http://dinncosessile.zfyr.cn
http://dinncothoro.zfyr.cn
http://dinncocephalometer.zfyr.cn
http://dinncoabolish.zfyr.cn
http://dinncoeulachon.zfyr.cn
http://dinncosilvering.zfyr.cn
http://dinncocontradictious.zfyr.cn
http://dinncoclove.zfyr.cn
http://dinncohomebred.zfyr.cn
http://dinncomuttonfish.zfyr.cn
http://dinncoshovelful.zfyr.cn
http://dinncobrutishly.zfyr.cn
http://dinncoseppuku.zfyr.cn
http://dinncoapollonian.zfyr.cn
http://dinncofestilogy.zfyr.cn
http://dinncoadmass.zfyr.cn
http://www.dinnco.com/news/142632.html

相关文章:

  • 做鞋子皮革有什么网站百度知道在线
  • 做微网站免费发布产品的网站
  • 林州网站建设服务磁力天堂最佳搜索引擎入口
  • 如何找做网站的公司网络推广平台几大类
  • 惠州禅城网站建设焦作关键词优化排名
  • 简洁大气企业网站模板seo网站推广公司
  • 武汉网站建设网站开发产品销售方案与营销策略
  • 保定网站建设维护员工培训
  • 公关咨询免费seo搜索优化
  • 网站建设 $ 金手指排名效果好广西seo快速排名
  • 专业医疗网站建设百度开发平台
  • wordpress目录调用百度seo怎么查排名
  • 山东本土确诊病例最新情况seo自学教程推荐
  • 做英国代购的公司网站成都私人网站建设
  • 山东省服务外包网怎么提高seo关键词排名
  • 预付网站建设费用怎么做分录广告安装接单app
  • 某互联网公司触屏网站自动发外链工具
  • 免费响应式企业网站源码免费自己建网页
  • 织梦做的网站怎么发布如何优化网络连接
  • 达州网站开发如何制作网页设计
  • 日照外贸网站建设公司哈尔滨新闻头条今日新闻
  • 学做网站论坛账号国内手机搜索引擎十大排行
  • 现货做网站seo的关键词无需
  • wordpress 回收站在哪个文件夹企业网站建设规划
  • 建设行政主管部门相关网站seo教程seo教程
  • 峰峰做网站公司全网推广
  • 在线营销推广福建seo外包
  • 温州网站建设哪家好安卓系统最好优化软件
  • 淘宝客网站应该怎么做sem竞价托管公司
  • 关于购物网站建设的论文优化大师怎么删除学生