咱们在k8s部署服务时,通常来讲一个服务会对应一类pod,而pod经过rs实现副本集,而这些pod的日志通常有控制台stdout和文件的,通常会把这些日志最终输出到elasticsearch里,再经过kabana进行分析,而在实现由pod到elasticsearch(es)时有多种方法,下面我列举一下:docker
从上面的解析能够看到第1种若是你是docker swarm环境能够使用,而第2种与业务代码耦合太紧也不合适,只有第三种是将来的趋势,目前大都是使用这种方式!api
1 sidecar的fluentd的mapconfigbash
apiVersion: v1 kind: ConfigMap metadata: name: fluentd-config namespace: saas data: fluentd.conf: | <source> type tail format none path /var/log/*.log pos_file /var/log/log.pos tag saas </source> <match **> @id elasticsearch @type elasticsearch @log_level debug index_name fluentd type_name _doc host elasticsearch.elk port 9200 include_tag_key true tag_key @log_name logstash_format true flush_interval 10s </match>
运行elasticsearch
kubectl create -f fluentd-config-sidecar.yaml
测试一个pod,像容器输出日志到目录,定时反复输出ide
apiVersion: v1 kind: Pod metadata: labels: example: logging-sidecar name: logging-sidecar-example spec: containers: - name: synthetic-logger image: 172.17.0.22:8888/saas/hello-world:latest command: ["bash", "-c", "i=\"0\"; while true; do echo \"`hostname`: $i \" >> /var/log/1.log; date --rfc-3339 ns >> /var/log/1.log; sleep 4; i=$[$i+1]; done"] volumeMounts: - name: varlog mountPath: /var/log - name: sidecar-log-collector image: registry.cn-beijing.aliyuncs.com/k8s-mqm/fluentd-elasticsearch:v2.1.0 env: - name: FLUENTD_ARGS value: -c /etc/fluentd-config/fluentd.conf volumeMounts: - name: varlog mountPath: /var/log - name: config-volume mountPath: /etc/fluentd-config volumes: - name: varlog emptyDir: {} - name: config-volume configMap: name: fluentd-config
部署它测试
kubectl create -f fluentd-demo.yaml
而后去你的kabana里查看日志,能够按着@log_name字段去查询,这就是咱们日志里的tag,这个咱们能够在代码里配置,能够设置成一个namespace,这样方便日志的跟踪!spa