本次任务展示如何在服务网格中自动的收集服务的一些遥测数据,在任务最后,一个新的metric和日志流会在网格中被启用.

在开始之前

  • 正确安装istio

收集新的数据

1.创建新的yaml文件,配置新的metric和日志流,istio会自动的生成和收集相应的数据

#cat  new_telemetry.yaml

# Configuration for metric instances
apiVersion: "config.istio.io/v1alpha2"
kind: metric
metadata:
  name: doublerequestcount
  namespace: istio-system
spec:
  value: "2" # count each request twice
  dimensions:
    source: source.service | "unknown"
    destination: destination.service | "unknown"
    message: '"twice the fun!"'
  monitored_resource_type: '"UNSPECIFIED"'
---
# Configuration for a Prometheus handler
apiVersion: "config.istio.io/v1alpha2"
kind: prometheus
metadata:
  name: doublehandler
  namespace: istio-system
spec:
  metrics:
  - name: double_request_count # Prometheus metric name
    instance_name: doublerequestcount.metric.istio-system # Mixer instance name (fully-qualified)
    kind: COUNTER
    label_names:
    - source
    - destination
    - message
---
# Rule to send metric instances to a Prometheus handler
apiVersion: "config.istio.io/v1alpha2"
kind: rule
metadata:
  name: doubleprom
  namespace: istio-system
spec:
  actions:
  - handler: doublehandler.prometheus
    instances:
    - doublerequestcount.metric
---
# Configuration for logentry instances
apiVersion: "config.istio.io/v1alpha2"
kind: logentry
metadata:
  name: newlog
  namespace: istio-system
spec:
  severity: '"warning"'
  timestamp: request.time
  variables:
    source: source.labels["app"] | source.service | "unknown"
    user: source.user | "unknown"
    destination: destination.labels["app"] | destination.service | "unknown"
    responseCode: response.code | 0
    responseSize: response.size | 0
    latency: response.duration | "0ms"
  monitored_resource_type: '"UNSPECIFIED"'
---
# Configuration for a stdio handler
apiVersion: "config.istio.io/v1alpha2"
kind: stdio
metadata:
  name: newhandler
  namespace: istio-system
spec:
 severity_levels:
   warning: 1 # Params.Level.WARNING
 outputAsJson: true
---
# Rule to send logentry instances to a stdio handler
apiVersion: "config.istio.io/v1alpha2"
kind: rule
metadata:
  name: newlogstdio
  namespace: istio-system
spec:
  match: "true" # match for all requests
  actions:
   - handler: newhandler.stdio
     instances:
     - newlog.logentry
---

2.push新的配置

# istioctl create -f new_telemetry.yaml
  1. 请求bookinfo的productpage页面

4.查看Prometheus的数据

5.查看请求日志刘

# kubectl -n istio-system logs $(kubectl -n istio-system get pods -l istio-mixer-type=telemetry -o jsonpath='{.items[0].metadata.name}') mixer | grep \"instance\":\"newlog.logentry.istio-system\"
{"level":"warn","time":"2018-07-09T06:27:10.697204Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"1.228702ms","responseCode":200,"responseSize":5,"source":"unknown","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:27:10.698311Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"988.062µs","responseCode":200,"responseSize":5,"source":"istio-ingressgateway.istio-system.svc.cluster.local","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:27:23.700682Z","instance":"newlog.logentry.istio-system","destination":"istio-policy.istio-system.svc.cluster.local","latency":"1.640487ms","responseCode":200,"responseSize":108,"source":"istio-ingressgateway.istio-system.svc.cluster.local","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:27:23.700179Z","instance":"newlog.logentry.istio-system","destination":"istio-ingressgateway.istio-system.svc.cluster.local","latency":"9.294168ms","responseCode":200,"responseSize":1795,"source":"unknown","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:27:24.701967Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"1.890863ms","responseCode":200,"responseSize":5,"source":"unknown","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:27:24.709841Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"3.608709ms","responseCode":200,"responseSize":5,"source":"istio-ingressgateway.istio-system.svc.cluster.local","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:28:47.750879Z","instance":"newlog.logentry.istio-system","destination":"istio-policy.istio-system.svc.cluster.local","latency":"1.926194ms","responseCode":200,"responseSize":108,"source":"istio-ingressgateway.istio-system.svc.cluster.local","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:28:47.749796Z","instance":"newlog.logentry.istio-system","destination":"istio-ingressgateway.istio-system.svc.cluster.local","latency":"8.979151ms","responseCode":200,"responseSize":1802,"source":"unknown","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:28:48.752131Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"2.019855ms","responseCode":200,"responseSize":5,"source":"unknown","user":"unknown"}
{"level":"warn","time":"2018-07-09T06:28:48.758448Z","instance":"newlog.logentry.istio-system","destination":"istio-telemetry.istio-system.svc.cluster.local","latency":"2.018155ms","responseCode":200,"responseSize":5,"source":"istio-ingressgateway.istio-system.svc.cluster.local","user":"unknown"}

了解telemetry配置

在本次任务中,我们添加了istio的配置,其指示Mixer对于网格中的流量,自动的生成和报告系的metric和新的日志流

增加的配置受到Mixer功能中的3中因素控制:

  1. 生成instance
  2. 创建handlers处理生成的instance
  3. Dispatch of instances to handlers _according to a set of _rules

理解metrics配置

metrics配置指示Mixer将metric发送到Prometheus,他使用了3个配置块:instance,handler,rule

kind: metric

此块定义了名为doublerequestcount的metric,该实例配置告诉Mixer如何生成metric值,以及其他需求,当然,这些基于Envoy(当然也包含Mixer自身)

对于doublerequestcount.metric的每个instance,配置指示Mixer为instance提供值为2,这意味着该metric记录值等于收到请求的总数的2倍

为每个doublerequestcount.metric实例指定一组dimensions,Dimensions提供了根据查询不同的需求和方向对metrics进行切片,聚合和分析,例如,可能需要在对应用程序行为进行故障排除时仅考虑对特定目标服务的查询请求

配置指示Mixer根据属性值以及表面值填充这些dimensions的值,例如,对于sourcedimension,新的配置从source.service属性获取值,如果未获取到该值,rule会指示Mixer使用默认的"unknown,对于messagedimension,使用文字值"twice the fun!"

kind: prometheus

此块定义了一个名叫doublehandler的handler,该handler的spec配置了Prometheus的metric标准,该值可以由Prometheus处理,该配置定义了一个名为double_request_count的指标,同时Prometheus adapter将istio_添加到命名空间之前,所以该metric在Prometheus中查询值为istio_double_request_count,该metric有3个label,其与doublerequestcount.metric相匹配

对于kind: prometheushandler,Mixer示例通过instance_name匹配Prometheus metrics, instance_name值必须是完全合格的Mixer 实例(例如:doublerequestcount.metric.istio-system)

在该块,定义了计数类型为COUNTER,此计数器使用metric块的value进行计数

kind: rule

此块定义了一个名为doubleprom的rule,该rule只是Mixer发送所有的doublerequestcount.metric实例到doublehandler.prometheus handler,并且这里没有match规则,该rule配置在默认的namespace,所以对网格中的所有请求都会执行规则

了解日志配置

日志配置指示Mixer将日志输出到stdout,他同样也使用了3个块配置,instance,handler,以及rule

kind: logentry

该块定义了一个名为newlog的schema ,用来生成日志,该instance告诉Mixer如何根据Envoy的报属性为request生成日志条目.

severity参数表明日志等级,在本例中,使用warning日志级别,该值将被logentry handler映射为支持的日志级别

timestamp参数提供日志项中的时间信息,在本例中,时间信息由request.time提供

variable参数允许配置每个logentry中应包含的值,一组表达式控制从istio属性和文字值到构成logentry的值的映射,本例中,每个logentry实例都包含了一个名为latency的字段,该字段填充了response.duration的值,如果没有获取到response.duration的值,latency字段会设置为默认的0ms.

kind: stdio

该模块定义了一个名为newhandler的handler,该handler的spec字段配置了stdio适配器如何处理收到的logentry instance, severity_levels参数控制了logentry的关于severity的值如何映射到支持的日志级别,本例中,warning被映射到WARING日志级别,outputAsJson参数顶一个适配器以json格式输出

kind: rule

该块顶一个了名为newlogstdio的rule,他将指示Mixer发送所有的newlog.logentry实例到newhandler.stdiohandler,本处match参数设置为true,所以该rule对网格中的所有请求执行规则

© w564791 all right reserved，powered by Gitbook文件修订时间： 2019-04-28 06:26:58

results matching ""

    No results matching ""