Zipkin call chain collector. Read the Zipkin call information from the Kafka, store the call information in the Elasticsearch, and facilitate the Zipkin front-end display.
Track the Zipkin version for iteration.
-
The application receives messages from Kafka and than insert these data into Elasticsearch.
-
These data are targets of monitor system.
-
Add the following items in the configuration file:
spring:
cloud:
stream:
kafka:
binder:
brokers: KAFKA_ADRESS
zkNodes: ZOOKEEPER_ADRESS
Make the monitoring data flow to Kafka.
helm install http://openchart.choerodon.com.cn/choerodon/devops/zipkin-collector --version=0.5.0
version
can be replaced. You can use the --set env.open.FOO_BAR=foobar
to override the environment variables.
Replaceable variable:
variable | definition |
---|---|
env.open.EUREKA_DEFAULT_ZONE |
eureka path |
env.open.SPRING_CLOUD_STREAM_KAFKA_BINDER_BROKERS |
kafka path |
env.open.SPRING_CLOUD_STREAM_KAFKA_BINDER_ZKNODES |
zookeeper path |
env.open.ZIPKIN_STORAGE_ELASTICSEARCH_HOSTS |
es path |
version |
chart version in helm install command |
依赖 | 版本 |
---|---|
zipkin | 1.31.3 |
choerodon-starter-hitoa | 0.5.0.RELEASE |
spring-cloud-sleuth-zipkin | 1.2.5.RELEASE |
spring-cloud-sleuth-zipkin-stream | 1.2.5.RELEASE |
spring-cloud-starter-stream-kafka | 1.2.1.RELEASE |
spring-cloud-stream-binder-kafka | 1.2.1.RELEASE |
If you find any shortcomings or bugs, please describe them in the issue.
Pull requests are welcome! Follow to know for more information on how to contribute.