line interface) can be used to fetch log data from containers. This data can be fed to an ELK (Elasticsearch, Logstash and Kibana) stack or Google Cloud logging for further analysis and visualization. we will not cover those here. For analysis and visualization, we will use the famous ELK (Elasticsearch, Logstash, Kibana) stack. To collect and forward the logs to the logging platform, we will use Stack and logspout Let’s first set up a simple ELK cluster on Kubernetes. In the real world, Elasticsearch should be set up with data, client and master as separate components so that they can be scaled

via the oc command or in the Kibana dashboard. OpenShift logging is based in the EFK stack (Elasticsearch, Fluentd and Kibana). The audit logs can be accessed via oc commands and can be forwarded to 3 Tanzu TKG ships with Fluent Bit for collecting and forwarding logs. Logs can go to an Elasticsearch, Kafka, Splunk, syslog or HTTP endpoint. The deployment and configuration of Fluent Bit is a Administrators can deploy the OpenShift Elasticsearch Operator and the OpenShift Logging Operator. Once installed, logs are collected, stored and visualized using Fluentd, Elasticsearch and Kibana. Logs can also be

使用AlertManager告警。 常用的一些exporter： • node_exporter • jmx_exporter • mysqld_exporter • redis_exporter • elasticsearch_exporter • …… 注：相比于基于Exporter的这种通用解决方案，业界一些成熟的开发框架或平台也会提供更加原生的监控解决方案，比如针 对Spring社区Spring B