初始化3.0.0版本

.gitignore

-### Intellij ###
-# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
-
-*.iml
-
-## Directory-based project format:
-.idea/
-# if you remove the above rule, at least ignore the following:
-
-# User-specific stuff:
-# .idea/workspace.xml
-# .idea/tasks.xml
-# .idea/dictionaries
-# .idea/shelf
-
-# Sensitive or high-churn files:
-.idea/dataSources.ids
-.idea/dataSources.xml
-.idea/sqlDataSources.xml
-.idea/dynamic.xml
-.idea/uiDesigner.xml
-
-
-# Mongo Explorer plugin:
-.idea/mongoSettings.xml
-
-## File-based project format:
-*.ipr
-*.iws
-
-## Plugin-specific files:
-
-# IntelliJ
-/out/
-
-# mpeltonen/sbt-idea plugin
-.idea_modules/
-
-# JIRA plugin
-atlassian-ide-plugin.xml
-
-# Crashlytics plugin (for Android Studio and IntelliJ)
-com_crashlytics_export_strings.xml
-crashlytics.properties
-crashlytics-build.properties
-fabric.properties
-
-
-### Java ###
-*.class
-
-# Mobile Tools for Java (J2ME)
-.mtj.tmp/
-
-# Package Files #
-*.jar
-*.war
-*.ear
-*.tar.gz
-
-# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
-hs_err_pid*
-
-
-### OSX ###
-.DS_Store
-.AppleDouble
-.LSOverride
-
-# Icon must end with two \r
-Icon
-
-
-# Thumbnails
-._*
-
-# Files that might appear in the root of a volume
-.DocumentRevisions-V100
-.fseventsd
-.Spotlight-V100
-.TemporaryItems
-.Trashes
-.VolumeIcon.icns
-
-# Directories potentially created on remote AFP share
-.AppleDB
-.AppleDesktop
-Network Trash Folder
-Temporary Items
-.apdisk
-
-/target
-target/
-*.log
-*.log.*
-*.bak
-*.vscode
-*/.vscode/*
-*/.vscode
-*/velocity.log*
-*/*.log
-*/*.log.*
-node_modules/
-node_modules/*
-workspace.xml
-/output/*
-.gitversion
-node_modules/*
-out/*
-dist/
-dist/*
-kafka-manager-web/src/main/resources/templates/
-.DS_Store
-kafka-manager-console/package-lock.json
+### Intellij ###
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and Webstorm
+
+*.iml
+
+## Directory-based project format:
+.idea/
+# if you remove the above rule, at least ignore the following:
+
+# User-specific stuff:
+# .idea/workspace.xml
+# .idea/tasks.xml
+# .idea/dictionaries
+# .idea/shelf
+
+# Sensitive or high-churn files:
+.idea/dataSources.ids
+.idea/dataSources.xml
+.idea/sqlDataSources.xml
+.idea/dynamic.xml
+.idea/uiDesigner.xml
+
+
+# Mongo Explorer plugin:
+.idea/mongoSettings.xml
+
+## File-based project format:
+*.ipr
+*.iws
+
+## Plugin-specific files:
+
+# IntelliJ
+/out/
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties
+
+
+### Java ###
+*.class
+
+# Mobile Tools for Java (J2ME)
+.mtj.tmp/
+
+# Package Files #
+*.jar
+*.war
+*.ear
+*.tar.gz
+
+# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
+hs_err_pid*
+
+
+### OSX ###
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+/target
+target/
+*.log
+*.log.*
+*.bak
+*.vscode
+*/.vscode/*
+*/.vscode
+*/velocity.log*
+*/*.log
+*/*.log.*
+node_modules/
+node_modules/*
+workspace.xml
+/output/*
+.gitversion
+out/*
+dist/
+dist/*
+km-rest/src/main/resources/templates/
+*dependency-reduced-pom*
\ No newline at end of file

CONTRIBUTING.md

@@ -7,7 +7,7 @@ Thanks for considering to contribute this project. All issues and pull requests
 Before sending pull request to this project, please read and follow guidelines below.
 
 1. Branch: We only accept pull request on `dev` branch.
-2. Coding style: Follow the coding style used in kafka-manager.
+2. Coding style: Follow the coding style used in LogiKM.
 3. Commit message: Use English and be aware of your spell.
 4. Test: Make sure to test your code.
 

Dockerfile

-ARG MAVEN_VERSION=3.8.4-openjdk-8-slim
-ARG JAVA_VERSION=8-jdk-alpine3.9
-FROM maven:${MAVEN_VERSION} AS builder
-ARG CONSOLE_ENABLE=true
-
-WORKDIR /opt
-COPY . .
-COPY distribution/conf/settings.xml /root/.m2/settings.xml
-
-# whether to build console
-RUN set -eux; \
-    if [ $CONSOLE_ENABLE = 'false' ]; then \
-        sed -i "/kafka-manager-console/d" pom.xml; \
-    fi \
-    && mvn -Dmaven.test.skip=true clean install -U
-
-FROM openjdk:${JAVA_VERSION}
-
-RUN sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories && apk add --no-cache tini
-
-ENV TZ=Asia/Shanghai
-ENV AGENT_HOME=/opt/agent/
-
-COPY --from=builder /opt/kafka-manager-web/target/kafka-manager.jar /opt
-COPY --from=builder /opt/container/dockerfiles/docker-depends/config.yaml $AGENT_HOME
-COPY --from=builder /opt/container/dockerfiles/docker-depends/jmx_prometheus_javaagent-0.15.0.jar $AGENT_HOME
-COPY --from=builder /opt/distribution/conf/application-docker.yml /opt
-
-WORKDIR /opt
-
-ENV JAVA_AGENT="-javaagent:$AGENT_HOME/jmx_prometheus_javaagent-0.15.0.jar=9999:$AGENT_HOME/config.yaml"
-ENV JAVA_HEAP_OPTS="-Xms1024M -Xmx1024M -Xmn100M "
-ENV JAVA_OPTS="-verbose:gc  \
-    -XX:MaxMetaspaceSize=256M  -XX:+DisableExplicitGC -XX:+UseStringDeduplication \
-    -XX:+UseG1GC  -XX:+HeapDumpOnOutOfMemoryError   -XX:-UseContainerSupport"
-
-EXPOSE 8080 9999
-
-ENTRYPOINT ["tini", "--"]
-
-CMD [ "sh", "-c", "java -jar $JAVA_AGENT $JAVA_HEAP_OPTS $JAVA_OPTS kafka-manager.jar --spring.config.location=application-docker.yml"]

README.md

-
----
-![KnowStreaing](https://user-images.githubusercontent.com/71620349/183546097-71451983-d00e-4ad4-afb0-43fb597c69a9.png)
-
-**一站式`Apache Kafka`管控平台**
-
-`LogiKM开源至今备受关注，考虑到开源项目应该更贴合Apache Kafka未来发展方向，经项目组慎重考虑，我们将其品牌升级成Know Streaming，新的大版本更新马上就绪，感谢大家一如既往的支持！也欢迎Kafka爱好者一起共建社区`
-
-阅读本README文档，您可以了解到滴滴Know Streaming的用户群体、产品定位等信息，并通过体验地址，快速体验Kafka集群指标监控与运维管控的全流程。
-
-
-## 1 产品简介
-滴滴Know Streaming脱胎于滴滴内部多年的Kafka运营实践经验，是面向Kafka用户、Kafka运维人员打造的共享多租户Kafka云平台。专注于Kafka运维管控、监控告警、资源治理等核心场景，经历过大规模集群、海量大数据的考验。内部满意度高达90%的同时，还与多家知名企业达成商业化合作。
-
-### 1.1 快速体验地址
-
-- 体验地址（新的体验地址马上就来） http://117.51.150.133:8080  账号密码 admin/admin
-
-### 1.2 体验地图
-相比较于同类产品的用户视角单一（大多为管理员视角），滴滴Logi-KafkaManager建立了基于分角色、多场景视角的体验地图。分别是：**用户体验地图、运维体验地图、运营体验地图**
-
-#### 1.2.1 用户体验地图
-- 平台租户申请  ：申请应用（App）作为Kafka中的用户名，并用 AppID+password作为身份验证
-- 集群资源申请  ：按需申请、按需使用。可使用平台提供的共享集群，也可为应用申请独立的集群
-- Topic   申   请  ：可根据应用（App）创建Topic，或者申请其他topic的读写权限
-- Topic   运   维  ：Topic数据采样、调整配额、申请分区等操作
-- 指   标  监   控  ：基于Topic生产消费各环节耗时统计，监控不同分位数性能指标
-- 消 费 组 运 维 ：支持将消费偏移重置至指定时间或指定位置
-
-#### 1.2.2 运维体验地图
-- 多版本集群管控  ：支持从`0.10.2`到`2.x`版本
-- 集    群    监   控  ：集群Topic、Broker等多维度历史与实时关键指标查看，建立健康分体系
-- 集    群    运   维  ：划分部分Broker作为Region，使用Region定义资源划分单位，并按照业务、保障能力区分逻辑集群
-- Broker    运    维  ：包括优先副本选举等操作
-- Topic      运    维  ：包括创建、查询、扩容、修改属性、迁移、下线等
-
-
-#### 1.2.3 运营体验地图
-- 资  源  治  理  ：沉淀资源治理方法。针对Topic分区热点、分区不足等高频常见问题，沉淀资源治理方法，实现资源治理专家化
-- 资  源  审  批  ：工单体系。Topic创建、调整配额、申请分区等操作，由专业运维人员审批，规范资源使用，保障平台平稳运行
-- 账  单  体  系  ：成本控制。Topic资源、集群资源按需申请、按需使用。根据流量核算费用，帮助企业建设大数据成本核算体系
-
-### 1.3 核心优势
-- 高 效 的 问 题 定 位  ：监控多项核心指标，统计不同分位数据，提供种类丰富的指标监控报表，帮助用户、运维人员快速高效定位问题
-- 便 捷 的 集 群 运 维  ：按照Region定义集群资源划分单位，将逻辑集群根据保障等级划分。在方便资源隔离、提高扩展能力的同时，实现对服务端的强管控
-- 专 业 的 资 源 治 理  ：基于滴滴内部多年运营实践，沉淀资源治理方法，建立健康分体系。针对Topic分区热点、分区不足等高频常见问题，实现资源治理专家化
-- 友 好 的 运 维 生 态  ：与Prometheus、Grafana、滴滴夜莺监控告警系统打通，集成指标分析、监控告警、集群部署、集群升级等能力。形成运维生态，凝练专家服务，使运维更高效
-
-### 1.4 滴滴Logi-KafkaManager架构图
-
-![kafka-manager-arch](https://img-ys011.didistatic.com/static/dicloudpub/do1_xgDHNDLj2ChKxctSuf72)
-
-
-## 2 相关文档
-
-### 2.1 产品文档
-- [滴滴Know Streaming 安装手册](docs/install_guide/install_guide_cn.md)
-- [滴滴Know Streaming 接入集群](docs/user_guide/add_cluster/add_cluster.md)
-- [滴滴Know Streaming 用户使用手册](docs/user_guide/user_guide_cn.md)
-- [滴滴Know Streaming FAQ](docs/user_guide/faq.md)
-
-### 2.2 社区文章
-- [滴滴云官网产品介绍](https://www.didiyun.com/production/logi-KafkaManager.html)
-- [7年沉淀之作--滴滴Logi日志服务套件](https://mp.weixin.qq.com/s/-KQp-Qo3WKEOc9wIR2iFnw)
-- [滴滴Know Streaming 一站式Kafka管控平台](https://mp.weixin.qq.com/s/9qSZIkqCnU6u9nLMvOOjIQ)
-- [滴滴Know Streaming 开源之路](https://xie.infoq.cn/article/0223091a99e697412073c0d64)
-- [滴滴Know Streaming 系列视频教程](https://space.bilibili.com/442531657/channel/seriesdetail?sid=571649)
-- [kafka最强最全知识图谱](https://www.szzdzhp.com/kafka/)
-- [滴滴Know Streaming新用户入门系列文章专栏 --石臻臻](https://www.szzdzhp.com/categories/LogIKM/)
-- [kafka实践（十五）：滴滴开源Kafka管控平台 Know Streaming研究--A叶子叶来](https://blog.csdn.net/yezonggang/article/details/113106244)
-- [基于云原生应用管理平台Rainbond安装 滴滴Know Streaming](https://www.rainbond.com/docs/opensource-app/logikm/?channel=logikm)
-
-## 3 Know Streaming开源用户交流群
-
-![image](https://user-images.githubusercontent.com/5287750/111266722-e531d800-8665-11eb-9242-3484da5a3099.png)  
-
-想跟各个大佬交流Kafka Es 等中间件/大数据相关技术请 加微信进群。
-
-微信加群：添加<font color=red>mike_zhangliang</font>、<font color=red>PenceXie</font>的微信号备注Know Streaming加群或关注公众号 云原生可观测性 回复 "Know Streaming加群"
-
-## 4 知识星球
-
-<img width="447" alt="image" src="https://user-images.githubusercontent.com/71620349/147314042-843a371a-48c0-4d9a-a65e-ca40236f3300.png">
-
-<br>
-<center>
-  ✅我们正在组建国内最大最权威的
-</center>
-<br>
-<center>
-<font color=red size=5><b>【Kafka中文社区】</b></font>
-</center>
-  
-在这里你可以结交各大互联网Kafka大佬以及3000+Kafka爱好者，一起实现知识共享，实时掌控最新行业资讯，期待您的加入中～https://z.didi.cn/5gSF9  
-
-<font color=red size=5>有问必答~！  </font>
-
-<font color=red size=5>互动有礼~！  </font>
-
-PS:提问请尽量把问题一次性描述清楚，并告知环境信息情况哦～！如使用版本、操作步骤、报错/警告信息等，方便大V们快速解答～
-
-## 5 项目成员
-
-### 5.1 内部核心人员
-
-`iceyuhui`、`liuyaguang`、`limengmonty`、`zhangliangmike`、`zhaoqingrong`、`xiepeng`、`nullhuangyiming`、`zengqiao`、`eilenexuzhe`、`huangjiaweihjw`、`zhaoyinrui`、`marzkonglingxu`、`joysunchao`、`石臻臻`
-
-
-### 5.2 外部贡献者
-
-`fangjunyu`、`zhoutaiyang`
-
-
-## 6 协议
-
-`Know Streaming`基于`Apache-2.0`协议进行分发和使用，更多信息参见[协议文件](./LICENSE)
-
-## 7 Star History
-
-[![Star History Chart](https://api.star-history.com/svg?repos=didi/KnowStreaming&type=Date)](https://star-history.com/#didi/KnowStreaming&Date)
-
+
+<p align="center">
+<img src="docs/assets/KnowStreamingLogo.png" width = "512" height = "129" div align=center />
+</p>
+
+<p align="center">
+    <a href="knowstreaming.com">产品官网</a> | 
+    <a href="https://github.com/didi/KnowStreaming/releases">下载地址</a> | 
+    <a href="doc.knowstreaming.com">文档资源</a> | 
+    <a href="demo.knowstreaming.com">体验环境</a> 
+</p>
+
+<p align="center">
+<!--最近一次提交时间-->
+<a href="https://img.shields.io/github/last-commit/didi/KnowStreaming">
+    <img src="https://img.shields.io/github/last-commit/didi/KnowStreaming" alt="LastCommit">
+</a>
+
+<!--最新版本-->
+<a href="https://github.com/didi/KnowStreaming/blob/master/LICENSE">
+    <img src="https://img.shields.io/github/v/release/didi/KnowStreaming" alt="License">
+</a>
+
+<!--License信息-->
+<a href="https://github.com/didi/KnowStreaming/blob/master/LICENSE">
+    <img src="https://img.shields.io/github/license/didi/KnowStreaming" alt="License">
+</a>
+
+<!--Open-Issue-->
+<a href="https://github.com/didi/KnowStreaming/issues">
+    <img src="https://img.shields.io/github/issues-raw/didi/KnowStreaming" alt="Issues">
+</a>
+
+<!--知识星球-->
+<a href="https://z.didi.cn/5gSF9">
+    <img src="https://img.shields.io/badge/join-%E7%9F%A5%E8%AF%86%E6%98%9F%E7%90%83-red" alt="Slack">
+</a>
+
+</p>
+
+
+---
+
+
+## `Know Streaming` 简介
+
+
+`Know Streaming`专注于Kafka运维管控、监控告警、资源治理、多活容灾等核心场景，经历大规模集群、海量大数据考验，在用户体验、监控、运维管控上进行了平台化、可视化、智能化的建设，提供一系列特色的功能，极大地方便了用户和运维人员的日常使用。与其他Kafka管控产品相比，`Know Streaming` 具有以下特点：
+
+- 👀 &nbsp;**简单易用**：提炼高频的 CLI 能力，设计合理的产品使用路径，绘制清新美观的 GUI 页面，始终将简单易用作为产品的主要目标。
+
+
+- 🌪️ &nbsp;**功能丰富**：主要包含`多集群管理`和`系统管理`两大块，具体包含：
+  1. 多集群管理：包括集群管理、Broker管理、Topic管理、Group管理、Security管理、Jobs管理等六大功能模块，几乎涵盖 CLI 的所有高频能力。
+  2. 系统管理：包括配置管理、用户管理、审计日志等3大功能模块，基本满足开源用户的使用需要。
+
+
+- 👏 &nbsp;**版本兼容**：支持 0.10 及以上，**`ZK`** 或 **`Raft`** 运行模式的Kafka版本，此外在兼容架构上具备良好的扩展性。
+
+
+- 🚀 &nbsp;**专业能力**：不仅是 CLI 到 GUI 的优秀翻译，更是涵盖一系列专业能力的产品，包括但不限于：
+  1. 观测提升： **`多维度指标观测大盘`**、**`观测指标最佳实践`** 等功能。
+  2. 异常巡检：**`集群多维度健康巡检`**、 **`集群多维度健康分`** 等功能。
+  3. 能力增强：**`Topic扩缩副本`**、**`Topic副本迁移`** 等功能。
+
+
+- ⚡️ &nbsp;**支持分布式**：具备水平扩展能力，只需要增加节点即可获取更强的采集及对外服务能力。
+
+&nbsp;
+**产品图**
+
+<p align="center">
+
+<img src="docs/assets/readme/KnowStreamingPageDemo.jpg" width = "768" height = "473" div align=center />
+
+</p>
+
+
+
+
+## 文档资源
+
+**`开发相关手册`**
+
+- [打包编译手册](docs/install_guide/源码编译打包手册.md)
+- [单机部署手册](docs/install_guide/单机部署手册.md)
+- [版本升级手册](docs/install_guide/版本升级手册.md)
+- [本地源码启动手册](docs/dev_guide/本地源码启动手册.md)
+
+**`产品相关手册`**
+
+- [产品使用指南](docs/user_guide/用户使用手册.md)
+- [2.x与3.x新旧对比手册](docs/user_guide/新旧对比手册.md)
+- [FAQ](docs/user_guide/faq.md)
+
+
+**点击 [这里](https://doc.knowstreaming.com/product/1-quick-start)，也可以从官网获取到更多文档**
+
+
+
+
+
+## 成为社区贡献者
+
+点击 [这里](CONTRIBUTING.md)，了解如何成为 Know Streaming 的贡献者
+
+
+
+## 加入技术交流群
+
+**`1、知识星球`**
+
+<p align="left">
+<img src="docs/assets/readme/ZSXQ.jpg" width = "512" height = "160" div align=left />
+</p>       
+
+<br/>
+<br/>
+<br/>
+<br/>
+<br/>
+<br/>
+<br/>
+<br/>
+
+👍 我们正在组建国内最大，最权威的 **[Kafka中文社区](https://z.didi.cn/5gSF9)**
+
+在这里你可以结交各大互联网的 Kafka大佬 以及 3000+ Kafka爱好者，一起实现知识共享，实时掌控最新行业资讯，期待 👏 &nbsp; 您的加入中～ https://z.didi.cn/5gSF9
+
+有问必答~！ 互动有礼~！
+
+PS: 提问请尽量把问题一次性描述清楚，并告知环境信息情况～！如使用版本、操作步骤、报错/警告信息等，方便大V们快速解答～
+
+&nbsp;
+
+**`2、微信群`**
+
+微信加群：添加`mike_zhangliang`、`danke-x`的微信号备注Logi加群。
\ No newline at end of file

Releases_Notes.md

 
 ---
 
-![kafka-manager-logo](./docs/assets/images/common/logo_name.png)
+![Logo](docs/assets/KnowStreamingLogo.png)
 
 **一站式`Apache Kafka`集群指标监控与运维管控平台**
 
 --- 
 
+
 ## v2.6.0
 
 版本上线时间：2022-01-24
@@ -40,6 +41,16 @@
 - 修复Dockerfile执行时提示缺少application.yml文件的问题
 - 修复逻辑集群更新时，会报空指针的问题
 
+
+## v2.5.0
+
+版本上线时间：2021-07-10
+
+### 体验优化
+- 更改产品名为LogiKM
+- 更新产品图标
+
+
 ## v2.4.1+
 
 版本上线时间：2021-05-21
@@ -49,7 +60,7 @@
 - 增加接口调用可绕过登录的功能(v2.4.1)
 
 ### 体验优化
-- tomcat 版本提升至8.5.66(v2.4.2)
+- Tomcat 版本提升至8.5.66(v2.4.2)
 - op接口优化，拆分util接口为topic、leader两类接口(v2.4.1)
 - 简化Gateway配置的Key长度(v2.4.1)
 

bin/init_es_template.sh

+esaddr=127.0.0.1
+port=8060
+curl -s --connect-timeout 10 -o /dev/null  http://${esaddr}:${port}/_cat/nodes >/dev/null 2>&1 
+if [ "$?" != "0" ];then
+    echo "Elasticserach 访问失败, 请安装完后检查并重新执行该脚本 "
+    exit
+fi
+
+curl -s --connect-timeout 10 -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_broker_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_broker_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "brokerId" : {
+          "type" : "long"
+        },
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "metrics" : {
+          "properties" : {
+            "NetworkProcessorAvgIdle" : {
+              "type" : "float"
+            },
+            "UnderReplicatedPartitions" : {
+              "type" : "float"
+            },
+            "BytesIn_min_15" : {
+              "type" : "float"
+            },
+            "HealthCheckTotal" : {
+              "type" : "float"
+            },
+            "RequestHandlerAvgIdle" : {
+              "type" : "float"
+            },
+            "connectionsCount" : {
+              "type" : "float"
+            },
+            "BytesIn_min_5" : {
+              "type" : "float"
+            },
+            "HealthScore" : {
+              "type" : "float"
+            },
+            "BytesOut" : {
+              "type" : "float"
+            },
+            "BytesOut_min_15" : {
+              "type" : "float"
+            },
+            "BytesIn" : {
+              "type" : "float"
+            },
+            "BytesOut_min_5" : {
+              "type" : "float"
+            },
+            "TotalRequestQueueSize" : {
+              "type" : "float"
+            },
+            "MessagesIn" : {
+              "type" : "float"
+            },
+            "TotalProduceRequests" : {
+              "type" : "float"
+            },
+            "HealthCheckPassed" : {
+              "type" : "float"
+            },
+            "TotalResponseQueueSize" : {
+              "type" : "float"
+            }
+          }
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }' 
+
+curl -s -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_cluster_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_cluster_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "metrics" : {
+          "properties" : {
+            "Connections" : {
+              "type" : "double"
+            },
+            "BytesIn_min_15" : {
+              "type" : "double"
+            },
+            "PartitionURP" : {
+              "type" : "double"
+            },
+            "HealthScore_Topics" : {
+              "type" : "double"
+            },
+            "EventQueueSize" : {
+              "type" : "double"
+            },
+            "ActiveControllerCount" : {
+              "type" : "double"
+            },
+            "GroupDeads" : {
+              "type" : "double"
+            },
+            "BytesIn_min_5" : {
+              "type" : "double"
+            },
+            "HealthCheckTotal_Topics" : {
+              "type" : "double"
+            },
+            "Partitions" : {
+              "type" : "double"
+            },
+            "BytesOut" : {
+              "type" : "double"
+            },
+            "Groups" : {
+              "type" : "double"
+            },
+            "BytesOut_min_15" : {
+              "type" : "double"
+            },
+            "TotalRequestQueueSize" : {
+              "type" : "double"
+            },
+            "HealthCheckPassed_Groups" : {
+              "type" : "double"
+            },
+            "TotalProduceRequests" : {
+              "type" : "double"
+            },
+            "HealthCheckPassed" : {
+              "type" : "double"
+            },
+            "TotalLogSize" : {
+              "type" : "double"
+            },
+            "GroupEmptys" : {
+              "type" : "double"
+            },
+            "PartitionNoLeader" : {
+              "type" : "double"
+            },
+            "HealthScore_Brokers" : {
+              "type" : "double"
+            },
+            "Messages" : {
+              "type" : "double"
+            },
+            "Topics" : {
+              "type" : "double"
+            },
+            "PartitionMinISR_E" : {
+              "type" : "double"
+            },
+            "HealthCheckTotal" : {
+              "type" : "double"
+            },
+            "Brokers" : {
+              "type" : "double"
+            },
+            "Replicas" : {
+              "type" : "double"
+            },
+            "HealthCheckTotal_Groups" : {
+              "type" : "double"
+            },
+            "GroupRebalances" : {
+              "type" : "double"
+            },
+            "MessageIn" : {
+              "type" : "double"
+            },
+            "HealthScore" : {
+              "type" : "double"
+            },
+            "HealthCheckPassed_Topics" : {
+              "type" : "double"
+            },
+            "HealthCheckTotal_Brokers" : {
+              "type" : "double"
+            },
+            "PartitionMinISR_S" : {
+              "type" : "double"
+            },
+            "BytesIn" : {
+              "type" : "double"
+            },
+            "BytesOut_min_5" : {
+              "type" : "double"
+            },
+            "GroupActives" : {
+              "type" : "double"
+            },
+            "MessagesIn" : {
+              "type" : "double"
+            },
+            "GroupReBalances" : {
+              "type" : "double"
+            },
+            "HealthCheckPassed_Brokers" : {
+              "type" : "double"
+            },
+            "HealthScore_Groups" : {
+              "type" : "double"
+            },
+            "TotalResponseQueueSize" : {
+              "type" : "double"
+            },
+            "Zookeepers" : {
+              "type" : "double"
+            },
+            "LeaderMessages" : {
+              "type" : "double"
+            },
+            "HealthScore_Cluster" : {
+              "type" : "double"
+            },
+            "HealthCheckPassed_Cluster" : {
+              "type" : "double"
+            },
+            "HealthCheckTotal_Cluster" : {
+              "type" : "double"
+            }
+          }
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "type" : "date"
+        }
+      }
+    },
+    "aliases" : { }
+   }' 
+
+curl -s -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_group_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_group_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "group" : {
+          "type" : "keyword"
+        },
+        "partitionId" : {
+          "type" : "long"
+        },
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "topic" : {
+          "type" : "keyword"
+        },
+        "metrics" : {
+          "properties" : {
+            "HealthScore" : {
+              "type" : "float"
+            },
+            "Lag" : {
+              "type" : "float"
+            },
+            "OffsetConsumed" : {
+              "type" : "float"
+            },
+            "HealthCheckTotal" : {
+              "type" : "float"
+            },
+            "HealthCheckPassed" : {
+              "type" : "float"
+            }
+          }
+        },
+        "groupMetric" : {
+          "type" : "keyword"
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }' 
+
+curl -s -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_partition_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_partition_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "brokerId" : {
+          "type" : "long"
+        },
+        "partitionId" : {
+          "type" : "long"
+        },
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "topic" : {
+          "type" : "keyword"
+        },
+        "metrics" : {
+          "properties" : {
+            "LogStartOffset" : {
+              "type" : "float"
+            },
+            "Messages" : {
+              "type" : "float"
+            },
+            "LogEndOffset" : {
+              "type" : "float"
+            }
+          }
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }' 
+
+curl -s -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_replication_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_partition_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "brokerId" : {
+          "type" : "long"
+        },
+        "partitionId" : {
+          "type" : "long"
+        },
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "topic" : {
+          "type" : "keyword"
+        },
+        "metrics" : {
+          "properties" : {
+            "LogStartOffset" : {
+              "type" : "float"
+            },
+            "Messages" : {
+              "type" : "float"
+            },
+            "LogEndOffset" : {
+              "type" : "float"
+            }
+          }
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }[root@10-255-0-23 template]# cat ks_kafka_replication_metric
+PUT _template/ks_kafka_replication_metric
+{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_replication_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }' 
+
+curl -s -o /dev/null -X POST -H 'cache-control: no-cache' -H 'content-type: application/json' http://${esaddr}:${port}/_template/ks_kafka_topic_metric -d '{
+    "order" : 10,
+    "index_patterns" : [
+      "ks_kafka_topic_metric*"
+    ],
+    "settings" : {
+      "index" : {
+        "number_of_shards" : "10"
+      }
+    },
+    "mappings" : {
+      "properties" : {
+        "brokerId" : {
+          "type" : "long"
+        },
+        "routingValue" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "topic" : {
+          "type" : "keyword"
+        },
+        "clusterPhyId" : {
+          "type" : "long"
+        },
+        "metrics" : {
+          "properties" : {
+            "BytesIn_min_15" : {
+              "type" : "float"
+            },
+            "Messages" : {
+              "type" : "float"
+            },
+            "BytesRejected" : {
+              "type" : "float"
+            },
+            "PartitionURP" : {
+              "type" : "float"
+            },
+            "HealthCheckTotal" : {
+              "type" : "float"
+            },
+            "ReplicationCount" : {
+              "type" : "float"
+            },
+            "ReplicationBytesOut" : {
+              "type" : "float"
+            },
+            "ReplicationBytesIn" : {
+              "type" : "float"
+            },
+            "FailedFetchRequests" : {
+              "type" : "float"
+            },
+            "BytesIn_min_5" : {
+              "type" : "float"
+            },
+            "HealthScore" : {
+              "type" : "float"
+            },
+            "LogSize" : {
+              "type" : "float"
+            },
+            "BytesOut" : {
+              "type" : "float"
+            },
+            "BytesOut_min_15" : {
+              "type" : "float"
+            },
+            "FailedProduceRequests" : {
+              "type" : "float"
+            },
+            "BytesIn" : {
+              "type" : "float"
+            },
+            "BytesOut_min_5" : {
+              "type" : "float"
+            },
+            "MessagesIn" : {
+              "type" : "float"
+            },
+            "TotalProduceRequests" : {
+              "type" : "float"
+            },
+            "HealthCheckPassed" : {
+              "type" : "float"
+            }
+          }
+        },
+        "brokerAgg" : {
+          "type" : "keyword"
+        },
+        "key" : {
+          "type" : "text",
+          "fields" : {
+            "keyword" : {
+              "ignore_above" : 256,
+              "type" : "keyword"
+            }
+          }
+        },
+        "timestamp" : {
+          "format" : "yyyy-MM-dd HH:mm:ss Z||yyyy-MM-dd HH:mm:ss||yyyy-MM-dd HH:mm:ss.SSS Z||yyyy-MM-dd HH:mm:ss.SSS||yyyy-MM-dd HH:mm:ss,SSS||yyyy/MM/dd HH:mm:ss||yyyy-MM-dd HH:mm:ss,SSS Z||yyyy/MM/dd HH:mm:ss,SSS Z||epoch_millis",
+          "index" : true,
+          "type" : "date",
+          "doc_values" : true
+        }
+      }
+    },
+    "aliases" : { }
+  }' 
+
+for i in {0..6};
+do
+    logdate=_$(date -d "${i} day ago" +%Y-%m-%d)
+    curl -s --connect-timeout 10 -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_broker_metric${logdate}  && \
+    curl -s -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_cluster_metric${logdate} && \
+    curl -s -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_group_metric${logdate} && \
+    curl -s -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_partition_metric${logdate} && \
+    curl -s -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_replication_metric${logdate} && \
+    curl -s -o /dev/null -X PUT http://${esaddr}:${port}/ks_kafka_topic_metric${logdate} || \
+    exit 2
+done
\ No newline at end of file

bin/shutdown.sh

+#!/bin/bash
+
+cd `dirname $0`/../libs
+target_dir=`pwd`
+
+pid=`ps ax | grep -i 'ks-km' | grep ${target_dir} | grep java | grep -v grep | awk '{print $1}'`
+if [ -z "$pid" ] ; then
+        echo "No ks-km running."
+        exit -1;
+fi
+
+echo "The ks-km (${pid}) is running..."
+
+kill ${pid}
+
+echo "Send shutdown request to ks-km (${pid}) OK"

bin/standalone-deploy.sh

+#!/bin/bash
+set -x
+
+function Install_Java(){
+	cd $dir
+	wget https://s3-gzpu.didistatic.com/pub/jdk11.tar.gz
+    tar -zxf $dir/jdk11.tar.gz -C /usr/local/
+    mv -f /usr/local/jdk-11.0.2 /usr/local/java11 >/dev/null 2>&1 
+    echo "export JAVA_HOME=/usr/local/java11" >> ~/.bashrc
+    echo "export CLASSPATH=/usr/java/java11/lib" >> ~/.bashrc
+    echo "export PATH=\$JAVA_HOME/bin:\$PATH:\$HOME/bin" >> ~/.bashrc
+    source ~/.bashrc
+}
+
+function Install_Mysql(){
+	cd $dir
+	wget https://s3-gzpu.didistatic.com/pub/mysql5.7.tar.gz
+	rpm -qa | grep -E "mariadb|mysql" | xargs yum -y remove >/dev/null 2>&1 
+	mv -f /var/lib/mysql/ /var/lib/mysqlbak$(date "+%s") >/dev/null 2>&1 
+	mkdir -p $dir/mysql/ && cd $dir/mysql/
+	tar -zxf $dir/mysql5.7.tar.gz -C $dir/mysql/
+	yum -y localinstall mysql* libaio*
+	systemctl start mysqld
+	systemctl enable mysqld >/dev/null 2>&1 
+	old_pass=`grep 'temporary password' /var/log/mysqld.log | awk '{print $NF}' | tail -n 1`
+	mysql -NBe "alter user USER() identified by '$mysql_pass';" --connect-expired-password -uroot -p$old_pass
+	if [ $? -eq 0 ];then
+		echo  "Mysql database installation completed"
+	else
+		echo "Mysql database configuration failed. The script exits"
+		exit
+	fi
+}
+
+function Install_ElasticSearch(){
+	kill -9 $(ps -ef | grep elasticsearch | grep -v "grep" | awk '{print $2}')  >/dev/null 2>&1   
+	id esuser  >/dev/null 2>&1  
+	if [ "$?" != "0" ];then
+		useradd esuser
+		echo "esuser soft nofile 655350" >>/etc/security/limits.conf
+		echo "esuser hard nofile 655350" >>/etc/security/limits.conf
+		echo "vm.max_map_count = 655360" >>/etc/sysctl.conf
+		sysctl -p >/dev/null 2>&1
+	fi
+	mkdir -p /km_es/es_data  && cd /km_es/ >/dev/null 2>&1
+	wget https://s3-gzpu.didistatic.com/pub/elasticsearch.tar.gz
+	tar -zxf elasticsearch.tar.gz -C /km_es/
+	chown -R esuser:esuser /km_es/
+	su - esuser <<-EOF
+		export JAVA_HOME=/usr/local/java11
+		sh /km_es/elasticsearch/control.sh start
+	EOF
+	sleep 5
+	es_status=`sh /km_es/elasticsearch/control.sh status | grep -o "started"`
+	if [ "$es_status" = "started" ];then
+		echo "elasticsearch started successfully～ "
+	else
+		echo "Elasticsearch failed to start. The script exited"
+		exit	
+	fi
+}
+
+function Install_KnowStreaming(){
+	cd $dir
+	wget https://s3-gzpu.didistatic.com/pub/knowstreaming/KnowStreaming-3.0.0-beta.tar.gz
+	tar -zxf KnowStreaming-3.0.0-beta.tar.gz -C $dir/
+	mysql -uroot -p$mysql_pass -e "create database know_streaming;"
+	mysql -uroot -p$mysql_pass  know_streaming < ./KnowStreaming/init/sql/ddl-ks-km.sql
+	mysql -uroot -p$mysql_pass  know_streaming < ./KnowStreaming/init/sql/ddl-logi-job.sql 
+    mysql -uroot -p$mysql_pass  know_streaming < ./KnowStreaming/init/sql/ddl-logi-security.sql
+    mysql -uroot -p$mysql_pass  know_streaming < ./KnowStreaming/init/sql/dml-ks-km.sql 
+    mysql -uroot -p$mysql_pass  know_streaming < ./KnowStreaming/init/sql/dml-logi.sql
+    sh ./KnowStreaming/init/template/template.sh
+    sed -i "s/mysql_pass/"$mysql_pass"/g" ./KnowStreaming/conf/application.yml
+    cd $dir/KnowStreaming/bin/ && sh startup.sh
+
+}
+
+dir=`pwd`
+mysql_pass=`date +%s |sha256sum |base64 |head -c 10 ;echo`"_Di2"
+echo "$mysql_pass" > $dir/mysql.password
+
+Install_Java
+Install_Mysql
+Install_ElasticSearch
+Install_KnowStreaming
\ No newline at end of file

bin/startup.sh

+error_exit ()
+{
+    echo "ERROR: $1 !!"
+    exit 1
+}
+
+[ ! -e "$JAVA_HOME/bin/java" ] && JAVA_HOME=$HOME/jdk/java
+[ ! -e "$JAVA_HOME/bin/java" ] && JAVA_HOME=/usr/java
+[ ! -e "$JAVA_HOME/bin/java" ] && unset JAVA_HOME
+
+if [ -z "$JAVA_HOME" ]; then
+  if $darwin; then
+
+    if [ -x '/usr/libexec/java_home' ] ; then
+      export JAVA_HOME=`/usr/libexec/java_home`
+
+    elif [ -d "/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home" ]; then
+      export JAVA_HOME="/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home"
+    fi
+  else
+    JAVA_PATH=`dirname $(readlink -f $(which javac))`
+    if [ "x$JAVA_PATH" != "x" ]; then
+      export JAVA_HOME=`dirname $JAVA_PATH 2>/dev/null`
+    fi
+  fi
+  if [ -z "$JAVA_HOME" ]; then
+        error_exit "Please set the JAVA_HOME variable in your environment, We need java(x64)! jdk8 or later is better!"
+  fi
+fi
+
+
+
+
+export WEB_SERVER="ks-km"
+export JAVA_HOME
+export JAVA="$JAVA_HOME/bin/java"
+export BASE_DIR=`cd $(dirname $0)/..; pwd`
+export CUSTOM_SEARCH_LOCATIONS=file:${BASE_DIR}/conf/
+
+
+#===========================================================================================
+# JVM Configuration
+#===========================================================================================
+
+JAVA_OPT="${JAVA_OPT} -server -Xms2g -Xmx2g -Xmn1g -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=320m"
+JAVA_OPT="${JAVA_OPT} -XX:-OmitStackTraceInFastThrow -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=${BASE_DIR}/logs/java_heapdump.hprof"
+
+## jdk版本高的情况 有些 参数废弃了
+JAVA_MAJOR_VERSION=$($JAVA -version 2>&1 | sed -E -n 's/.* version "([0-9]*).*$/\1/p')
+if [[ "$JAVA_MAJOR_VERSION" -ge "9" ]] ; then
+  JAVA_OPT="${JAVA_OPT} -Xlog:gc*:file=${BASE_DIR}/logs/km_gc.log:time,tags:filecount=10,filesize=102400"
+else
+  JAVA_OPT="${JAVA_OPT} -Djava.ext.dirs=${JAVA_HOME}/jre/lib/ext:${JAVA_HOME}/lib/ext"
+  JAVA_OPT="${JAVA_OPT} -Xloggc:${BASE_DIR}/logs/km_gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M"
+
+fi
+
+JAVA_OPT="${JAVA_OPT} -jar ${BASE_DIR}/libs/${WEB_SERVER}.jar"
+JAVA_OPT="${JAVA_OPT} --spring.config.additional-location=${CUSTOM_SEARCH_LOCATIONS}"
+JAVA_OPT="${JAVA_OPT} --logging.config=${BASE_DIR}/conf/logback-spring.xml"
+JAVA_OPT="${JAVA_OPT} --server.max-http-header-size=524288"
+
+
+
+if [ ! -d "${BASE_DIR}/logs" ]; then
+  mkdir ${BASE_DIR}/logs
+fi
+
+echo "$JAVA ${JAVA_OPT}"
+
+# check the start.out log output file
+if [ ! -f "${BASE_DIR}/logs/start.out" ]; then
+  touch "${BASE_DIR}/logs/start.out"
+fi
+
+# start
+echo -e "---- 启动脚本 ------\n $JAVA ${JAVA_OPT}" > ${BASE_DIR}/logs/start.out 2>&1 &
+
+
+nohup $JAVA ${JAVA_OPT} >> ${BASE_DIR}/logs/start.out 2>&1 &
+
+echo "${WEB_SERVER} is starting，you can check the ${BASE_DIR}/logs/start.out"

container/dockerfiles/docker-depends/config.yaml

----
-    startDelaySeconds: 0
-    ssl: false
-    lowercaseOutputName: false
-    lowercaseOutputLabelNames: false

container/dockerfiles/mysql/Dockerfile

-FROM mysql:5.7.37
-
-COPY mysqld.cnf /etc/mysql/mysql.conf.d/
-ENV TZ=Asia/Shanghai
-ENV MYSQL_ROOT_PASSWORD=root
-
-RUN apt-get update \
-    && apt -y install wget \
-    && wget https://ghproxy.com/https://raw.githubusercontent.com/didi/LogiKM/master/distribution/conf/create_mysql_table.sql -O /docker-entrypoint-initdb.d/create_mysql_table.sql
-
-EXPOSE 3306
-
-VOLUME ["/var/lib/mysql"]
\ No newline at end of file

container/dockerfiles/mysql/mysqld.cnf

-[client]
-default-character-set = utf8  
-
-[mysqld]
-character_set_server = utf8  
-pid-file        = /var/run/mysqld/mysqld.pid
-socket          = /var/run/mysqld/mysqld.sock
-datadir         = /var/lib/mysql
-symbolic-links=0
-
-max_allowed_packet = 10M
-sort_buffer_size = 1M
-read_rnd_buffer_size = 2M
-max_connections=2000
-
-lower_case_table_names=1
-character-set-server=utf8
-
-max_allowed_packet = 1G
-sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
-group_concat_max_len = 102400
-default-time-zone = '+08:00'
-[mysql]
-default-character-set = utf8
\ No newline at end of file

container/helm/Chart.lock

-dependencies:
-- name: mysql
-  repository: https://charts.bitnami.com/bitnami
-  version: 8.6.3
-digest: sha256:d250c463c1d78ba30a24a338a06a551503c7a736621d974fe4999d2db7f6143e
-generated: "2021-06-24T11:34:54.625217+08:00"

container/helm/Chart.yaml

-apiVersion: v2
-name: didi-km
-description: Logi-KafkaManager
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
-type: application
-
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
-appVersion: "2.4.2"
-dependencies:
-  - condition: mysql.enabled
-    name: mysql
-    repository: https://charts.bitnami.com/bitnami
-    version: 8.x.x

container/helm/templates/NOTES.txt

-1. Get the application URL by running these commands:
-{{- if .Values.ingress.enabled }}
-{{- range $host := .Values.ingress.hosts }}
-  {{- range .paths }}
-  http{{ if $.Values.ingress.tls }}s{{ end }}://{{ $host.host }}{{ .path }}
-  {{- end }}
-{{- end }}
-{{- else if contains "NodePort" .Values.service.type }}
-  export NODE_PORT=$(kubectl get --namespace {{ .Release.Namespace }} -o jsonpath="{.spec.ports[0].nodePort}" services {{ include "didi-km.fullname" . }})
-  export NODE_IP=$(kubectl get nodes --namespace {{ .Release.Namespace }} -o jsonpath="{.items[0].status.addresses[0].address}")
-  echo http://$NODE_IP:$NODE_PORT
-{{- else if contains "LoadBalancer" .Values.service.type }}
-     NOTE: It may take a few minutes for the LoadBalancer IP to be available.
-           You can watch the status of by running 'kubectl get --namespace {{ .Release.Namespace }} svc -w {{ include "didi-km.fullname" . }}'
-  export SERVICE_IP=$(kubectl get svc --namespace {{ .Release.Namespace }} {{ include "didi-km.fullname" . }} --template "{{"{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}"}}")
-  echo http://$SERVICE_IP:{{ .Values.service.port }}
-{{- else if contains "ClusterIP" .Values.service.type }}
-  export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "didi-km.name" . }},app.kubernetes.io/instance={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}")
-  export CONTAINER_PORT=$(kubectl get pod --namespace {{ .Release.Namespace }} $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
-  echo "Visit http://127.0.0.1:8080 to use your application"
-  kubectl --namespace {{ .Release.Namespace }} port-forward $POD_NAME 8080:$CONTAINER_PORT
-{{- end }}

container/helm/templates/_helpers.tpl

-{{/*
-Expand the name of the chart.
-*/}}
-{{- define "didi-km.name" -}}
-{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" }}
-{{- end }}
-
-{{/*
-Create a default fully qualified app name.
-We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
-If release name contains chart name it will be used as a full name.
-*/}}
-{{- define "didi-km.fullname" -}}
-{{- if .Values.fullnameOverride }}
-{{- .Values.fullnameOverride | trunc 63 | trimSuffix "-" }}
-{{- else }}
-{{- $name := default .Chart.Name .Values.nameOverride }}
-{{- if contains $name .Release.Name }}
-{{- .Release.Name | trunc 63 | trimSuffix "-" }}
-{{- else }}
-{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" }}
-{{- end }}
-{{- end }}
-{{- end }}
-
-{{/*
-Create chart name and version as used by the chart label.
-*/}}
-{{- define "didi-km.chart" -}}
-{{- printf "%s-%s" .Chart.Name .Chart.Version | replace "+" "_" | trunc 63 | trimSuffix "-" }}
-{{- end }}
-
-{{/*
-Common labels
-*/}}
-{{- define "didi-km.labels" -}}
-helm.sh/chart: {{ include "didi-km.chart" . }}
-{{ include "didi-km.selectorLabels" . }}
-{{- if .Chart.AppVersion }}
-app.kubernetes.io/version: {{ .Chart.AppVersion | quote }}
-{{- end }}
-app.kubernetes.io/managed-by: {{ .Release.Service }}
-{{- end }}
-
-{{/*
-Selector labels
-*/}}
-{{- define "didi-km.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "didi-km.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-{{- end }}
-
-{{/*
-Create the name of the service account to use
-*/}}
-{{- define "didi-km.serviceAccountName" -}}
-{{- if .Values.serviceAccount.create }}
-{{- default (include "didi-km.fullname" .) .Values.serviceAccount.name }}
-{{- else }}
-{{- default "default" .Values.serviceAccount.name }}
-{{- end }}
-{{- end }}

container/helm/templates/configmap.yaml

-{{- define "datasource.mysql" -}}
-{{- if .Values.mysql.enabled }}
-    {{- printf "%s-mysql" (include "didi-km.fullname" .) -}}
-{{- else -}}
-    {{- printf "%s" .Values.externalDatabase.host -}}
-{{- end -}}
-{{- end -}}
-
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: {{ include "didi-km.fullname" . }}-configs
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-data:
-  application.yml: |
-    server:
-      port: 8080
-      tomcat:
-        accept-count: 1000
-        max-connections: 10000
-        max-threads: 800
-        min-spare-threads: 100
-
-    spring:
-      application:
-        name: kafkamanager
-      datasource:
-        kafka-manager:
-          jdbc-url: jdbc:mysql://{{ include "datasource.mysql" . }}:3306/{{ .Values.mysql.auth.database }}?characterEncoding=UTF-8&serverTimezone=GMT%2B8&useSSL=false
-          username: {{ .Values.mysql.auth.username }}
-          password: {{ .Values.mysql.auth.password }}
-          driver-class-name: com.mysql.jdbc.Driver
-      main:
-        allow-bean-definition-overriding: true
-
-      profiles:
-        active: dev
-      servlet:
-        multipart:
-          max-file-size: 100MB
-          max-request-size: 100MB
-
-    logging:
-      config: classpath:logback-spring.xml
-
-    custom:
-      idc: cn
-      jmx:
-        max-conn: 20
-      store-metrics-task:
-        community:
-          broker-metrics-enabled: true
-          topic-metrics-enabled: true
-        didi:
-          app-topic-metrics-enabled: false
-          topic-request-time-metrics-enabled: false
-          topic-throttled-metrics-enabled: false
-        save-days: 7
-
-    # 任务相关的开关
-    task:
-      op:
-        sync-topic-enabled: false # 未落盘的Topic定期同步到DB中
-
-    account:
-      # ldap settings
-      ldap:
-        enabled: false
-        url: ldap://127.0.0.1:389/
-        basedn: dc=tsign,dc=cn
-        factory: com.sun.jndi.ldap.LdapCtxFactory
-        filter: sAMAccountName
-        security:
-          authentication: simple
-          principal: cn=admin,dc=tsign,dc=cn
-          credentials: admin
-        auth-user-registration: false
-        auth-user-registration-role: normal
-
-    kcm:
-      enabled: false
-      storage:
-        base-url: http://127.0.0.1
-      n9e:
-        base-url: http://127.0.0.1:8004
-        user-token: 12345678
-        timeout: 300
-        account: root
-        script-file: kcm_script.sh
-
-    monitor:
-      enabled: false
-      n9e:
-        nid: 2
-        user-token: 1234567890
-        mon:
-          base-url: http://127.0.0.1:8032
-        sink:
-          base-url: http://127.0.0.1:8006
-        rdb:
-          base-url: http://127.0.0.1:80
-
-    notify:
-      kafka:
-        cluster-id: 95
-        topic-name: didi-kafka-notify
-      order:
-        detail-url: http://127.0.0.1
-     

container/helm/templates/deployment.yaml

-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: {{ include "didi-km.fullname" . }}
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-spec:
-  {{- if not .Values.autoscaling.enabled }}
-  replicas: {{ .Values.replicaCount }}
-  {{- end }}
-  selector:
-    matchLabels:
-      {{- include "didi-km.selectorLabels" . | nindent 6 }}
-  template:
-    metadata:
-      {{- with .Values.podAnnotations }}
-      annotations:
-        {{- toYaml . | nindent 8 }}
-      {{- end }}
-      labels:
-        {{- include "didi-km.selectorLabels" . | nindent 8 }}
-    spec:
-      {{- with .Values.imagePullSecrets }}
-      imagePullSecrets:
-        {{- toYaml . | nindent 8 }}
-      {{- end }}
-      serviceAccountName: {{ include "didi-km.serviceAccountName" . }}
-      securityContext:
-        {{- toYaml .Values.podSecurityContext | nindent 8 }}
-      containers:
-        - name: {{ .Chart.Name }}
-          securityContext:
-            {{- toYaml .Values.securityContext | nindent 12 }}
-          image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
-          imagePullPolicy: {{ .Values.image.pullPolicy }}
-          ports:
-          - name: http
-            containerPort: 8080
-            protocol: TCP
-          - name: jmx-metrics
-            containerPort: 9999
-            protocol: TCP
-          resources:
-            {{- toYaml .Values.resources | nindent 12 }}
-          volumeMounts:
-          - name: configs
-            mountPath: /tmp/application.yml
-            subPath:  application.yml
-      {{- with .Values.nodeSelector }}
-      nodeSelector:
-        {{- toYaml . | nindent 8 }}
-      {{- end }}
-      {{- with .Values.affinity }}
-      affinity:
-        {{- toYaml . | nindent 8 }}
-      {{- end }}
-      {{- with .Values.tolerations }}
-      tolerations:
-        {{- toYaml . | nindent 8 }}
-      {{- end }}
-      volumes:
-      - name: configs
-        configMap:
-          name: {{ include "didi-km.fullname" . }}-configs

container/helm/templates/hpa.yaml

-{{- if .Values.autoscaling.enabled }}
-apiVersion: autoscaling/v2beta1
-kind: HorizontalPodAutoscaler
-metadata:
-  name: {{ include "didi-km.fullname" . }}
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-spec:
-  scaleTargetRef:
-    apiVersion: apps/v1
-    kind: Deployment
-    name: {{ include "didi-km.fullname" . }}
-  minReplicas: {{ .Values.autoscaling.minReplicas }}
-  maxReplicas: {{ .Values.autoscaling.maxReplicas }}
-  metrics:
-    {{- if .Values.autoscaling.targetCPUUtilizationPercentage }}
-    - type: Resource
-      resource:
-        name: cpu
-        targetAverageUtilization: {{ .Values.autoscaling.targetCPUUtilizationPercentage }}
-    {{- end }}
-    {{- if .Values.autoscaling.targetMemoryUtilizationPercentage }}
-    - type: Resource
-      resource:
-        name: memory
-        targetAverageUtilization: {{ .Values.autoscaling.targetMemoryUtilizationPercentage }}
-    {{- end }}
-{{- end }}

container/helm/templates/ingress.yaml

-{{- if .Values.ingress.enabled -}}
-{{- $fullName := include "didi-km.fullname" . -}}
-{{- $svcPort := .Values.service.port -}}
-{{- if semverCompare ">=1.14-0" .Capabilities.KubeVersion.GitVersion -}}
-apiVersion: networking.k8s.io/v1beta1
-{{- else -}}
-apiVersion: extensions/v1beta1
-{{- end }}
-kind: Ingress
-metadata:
-  name: {{ $fullName }}
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-  {{- with .Values.ingress.annotations }}
-  annotations:
-    {{- toYaml . | nindent 4 }}
-  {{- end }}
-spec:
-  {{- if .Values.ingress.tls }}
-  tls:
-    {{- range .Values.ingress.tls }}
-    - hosts:
-        {{- range .hosts }}
-        - {{ . | quote }}
-        {{- end }}
-      secretName: {{ .secretName }}
-    {{- end }}
-  {{- end }}
-  rules:
-    {{- range .Values.ingress.hosts }}
-    - host: {{ .host | quote }}
-      http:
-        paths:
-          {{- range .paths }}
-          - path: {{ .path }}
-            backend:
-              serviceName: {{ $fullName }}
-              servicePort: {{ $svcPort }}
-          {{- end }}
-    {{- end }}
-  {{- end }}

container/helm/templates/service.yaml

-apiVersion: v1
-kind: Service
-metadata:
-  name: {{ include "didi-km.fullname" . }}
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-spec:
-  type: {{ .Values.service.type }}
-  ports:
-    - port: {{ .Values.service.port }}
-      targetPort: http
-      protocol: TCP
-      name: http
-  selector:
-    {{- include "didi-km.selectorLabels" . | nindent 4 }}

container/helm/templates/serviceaccount.yaml

-{{- if .Values.serviceAccount.create -}}
-apiVersion: v1
-kind: ServiceAccount
-metadata:
-  name: {{ include "didi-km.serviceAccountName" . }}
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-  {{- with .Values.serviceAccount.annotations }}
-  annotations:
-    {{- toYaml . | nindent 4 }}
-  {{- end }}
-{{- end }}

container/helm/templates/tests/test-connection.yaml

-apiVersion: v1
-kind: Pod
-metadata:
-  name: "{{ include "didi-km.fullname" . }}-test-connection"
-  labels:
-    {{- include "didi-km.labels" . | nindent 4 }}
-  annotations:
-    "helm.sh/hook": test
-spec:
-  containers:
-    - name: wget
-      image: busybox
-      command: ['wget']
-      args: ['{{ include "didi-km.fullname" . }}:{{ .Values.service.port }}']
-  restartPolicy: Never

container/helm/values.yaml

-# Default values for didi-km.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-replicaCount: 1
-
-image:
-  repository: docker.io/fengxsong/logi-kafka-manager
-  pullPolicy: IfNotPresent
-  # Overrides the image tag whose default is the chart appVersion.
-  tag: "v2.4.2"
-
-imagePullSecrets: []
-nameOverride: ""
-# fullnameOverride must set same as release name
-fullnameOverride: "km"
-
-serviceAccount:
-  # Specifies whether a service account should be created
-  create: true
-  # Annotations to add to the service account
-  annotations: {}
-  # The name of the service account to use.
-  # If not set and create is true, a name is generated using the fullname template
-  name: ""
-
-podAnnotations: {}
-
-podSecurityContext: {}
-  # fsGroup: 2000
-
-securityContext: {}
-  # capabilities:
-  #   drop:
-  #   - ALL
-  # readOnlyRootFilesystem: true
-  # runAsNonRoot: true
-  # runAsUser: 1000
-
-service:
-  type: ClusterIP
-  port: 8080
-
-ingress:
-  enabled: false
-  annotations: {}
-    # kubernetes.io/ingress.class: nginx
-    # kubernetes.io/tls-acme: "true"
-  hosts:
-    - host: chart-example.local
-      paths: []
-  tls: []
-  #  - secretName: chart-example-tls
-  #    hosts:
-  #      - chart-example.local
-
-resources: 
-  # We usually recommend not to specify default resources and to leave this as a conscious
-  # choice for the user. This also increases chances charts run on environments with little
-  # resources, such as Minikube. If you do want to specify resources, uncomment the following
-  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-  limits:
-    cpu: 500m
-    memory: 2048Mi
-  requests:
-    cpu: 100m
-    memory: 200Mi
-
-autoscaling:
-  enabled: false
-  minReplicas: 1
-  maxReplicas: 100
-  targetCPUUtilizationPercentage: 80
-  # targetMemoryUtilizationPercentage: 80
-
-nodeSelector: {}
-
-tolerations: []
-
-affinity: {}
-
-# more configurations are set with configmap in file template/configmap.yaml
-externalDatabase:
-  host: ""
-mysql:
-  # if enabled is set to false, then you should manually specified externalDatabase.host
-  enabled: true
-  architecture: standalone
-  auth:
-    rootPassword: "s3cretR00t"
-    database: "logi_kafka_manager"
-    username: "logi_kafka_manager"
-    password: "n0tp@55w0rd"

distribution/bin/shutdown.sh

-#!/bin/bash
-
-cd `dirname $0`/../target
-target_dir=`pwd`
-
-pid=`ps ax | grep -i 'kafka-manager' | grep ${target_dir} | grep java | grep -v grep | awk '{print $1}'`
-if [ -z "$pid" ] ; then
-        echo "No kafka-manager running."
-        exit -1;
-fi
-
-echo "The kafka-manager (${pid}) is running..."
-
-kill ${pid}
-
-echo "Send shutdown request to kafka-manager (${pid}) OK"

distribution/bin/startup.sh

-error_exit ()
-{
-    echo "ERROR: $1 !!"
-    exit 1
-}
-
-[ ! -e "$JAVA_HOME/bin/java" ] && JAVA_HOME=$HOME/jdk/java
-[ ! -e "$JAVA_HOME/bin/java" ] && JAVA_HOME=/usr/java
-[ ! -e "$JAVA_HOME/bin/java" ] && unset JAVA_HOME
-
-if [ -z "$JAVA_HOME" ]; then
-  if $darwin; then
-
-    if [ -x '/usr/libexec/java_home' ] ; then
-      export JAVA_HOME=`/usr/libexec/java_home`
-
-    elif [ -d "/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home" ]; then
-      export JAVA_HOME="/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home"
-    fi
-  else
-    JAVA_PATH=`dirname $(readlink -f $(which javac))`
-    if [ "x$JAVA_PATH" != "x" ]; then
-      export JAVA_HOME=`dirname $JAVA_PATH 2>/dev/null`
-    fi
-  fi
-  if [ -z "$JAVA_HOME" ]; then
-        error_exit "Please set the JAVA_HOME variable in your environment, We need java(x64)! jdk8 or later is better!"
-  fi
-fi
-
-
-
-
-export WEB_SERVER="kafka-manager"
-export JAVA_HOME
-export JAVA="$JAVA_HOME/bin/java"
-export BASE_DIR=`cd $(dirname $0)/..; pwd`
-export CUSTOM_SEARCH_LOCATIONS=file:${BASE_DIR}/conf/
-
-
-#===========================================================================================
-# JVM Configuration
-#===========================================================================================
-
-JAVA_OPT="${JAVA_OPT} -server -Xms2g -Xmx2g -Xmn1g -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=320m"
-JAVA_OPT="${JAVA_OPT} -XX:-OmitStackTraceInFastThrow -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=${BASE_DIR}/logs/java_heapdump.hprof"
-
-## jdk版本高的情况 有些 参数废弃了
-JAVA_MAJOR_VERSION=$($JAVA -version 2>&1 | sed -E -n 's/.* version "([0-9]*).*$/\1/p')
-if [[ "$JAVA_MAJOR_VERSION" -ge "9" ]] ; then
-  JAVA_OPT="${JAVA_OPT} -Xlog:gc*:file=${BASE_DIR}/logs/km_gc.log:time,tags:filecount=10,filesize=102400"
-else
-  JAVA_OPT="${JAVA_OPT} -Djava.ext.dirs=${JAVA_HOME}/jre/lib/ext:${JAVA_HOME}/lib/ext"
-  JAVA_OPT="${JAVA_OPT} -Xloggc:${BASE_DIR}/logs/km_gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M"
-
-fi
-
-JAVA_OPT="${JAVA_OPT} -jar ${BASE_DIR}/target/${WEB_SERVER}.jar"
-JAVA_OPT="${JAVA_OPT} --spring.config.additional-location=${CUSTOM_SEARCH_LOCATIONS}"
-JAVA_OPT="${JAVA_OPT} --logging.config=${BASE_DIR}/conf/logback-spring.xml"
-JAVA_OPT="${JAVA_OPT} --server.max-http-header-size=524288"
-
-
-
-if [ ! -d "${BASE_DIR}/logs" ]; then
-  mkdir ${BASE_DIR}/logs
-fi
-
-echo "$JAVA ${JAVA_OPT}"
-
-# check the start.out log output file
-if [ ! -f "${BASE_DIR}/logs/start.out" ]; then
-  touch "${BASE_DIR}/logs/start.out"
-fi
-# start
-echo -e "---- 启动脚本 ------\n $JAVA ${JAVA_OPT}" > ${BASE_DIR}/logs/start.out 2>&1 &
-
-
-nohup $JAVA ${JAVA_OPT} >> ${BASE_DIR}/logs/start.out 2>&1 &
-
-echo "${WEB_SERVER} is starting，you can check the ${BASE_DIR}/logs/start.out"

distribution/conf/application-docker.yml

-
-## kafka-manager的配置文件，该文件中的配置会覆盖默认配置
-## 下面的配置信息基本就是jar中的 application.yml默认配置了;
-## 可以只修改自己变更的配置,其他的删除就行了; 比如只配置一下mysql
-
-
-server:
-  port: 8080
-  tomcat:
-    accept-count: 1000
-    max-connections: 10000
-    max-threads: 800
-    min-spare-threads: 100
-
-spring:
-  application:
-    name: kafkamanager
-    version: 2.6.0
-  profiles:
-    active: dev
-  datasource:
-    kafka-manager:
-      jdbc-url: jdbc:mysql://${LOGI_MYSQL_HOST:mysql}:${LOGI_MYSQL_PORT:3306}/${LOGI_MYSQL_DATABASE:logi_kafka_manager}?characterEncoding=UTF-8&useSSL=false&serverTimezone=GMT%2B8
-      username: ${LOGI_MYSQL_USER:root}
-      password: ${LOGI_MYSQL_PASSWORD:root}
-      driver-class-name: com.mysql.cj.jdbc.Driver
-  main:
-    allow-bean-definition-overriding: true
\ No newline at end of file

distribution/conf/application.yml

-
-## kafka-manager的配置文件，该文件中的配置会覆盖默认配置
-## 下面的配置信息基本就是jar中的 application.yml默认配置了;
-## 可以只修改自己变更的配置,其他的删除就行了; 比如只配置一下mysql
-
-
-server:
-  port: 8080
-  tomcat:
-    accept-count: 1000
-    max-connections: 10000
-    max-threads: 800
-    min-spare-threads: 100
-
-spring:
-  application:
-    name: kafkamanager
-  profiles:
-    active: dev
-  datasource:
-    kafka-manager:
-      jdbc-url: jdbc:mysql://localhost:3306/logi_kafka_manager?characterEncoding=UTF-8&useSSL=false&serverTimezone=GMT%2B8
-      username: root
-      password: 123456
-      driver-class-name: com.mysql.cj.jdbc.Driver
-  main:
-    allow-bean-definition-overriding: true
-

distribution/conf/application.yml.example

-
-## kafka-manager的配置文件，该文件中的配置会覆盖默认配置
-## 下面的配置信息基本就是jar中的 application.yml默认配置了;
-## 可以只修改自己变更的配置,其他的删除就行了; 比如只配置一下mysql
-
-
-server:
-  port: 8080
-  tomcat:
-    accept-count: 1000
-    max-connections: 10000
-    max-threads: 800
-    min-spare-threads: 100
-
-spring:
-  application:
-    name: kafkamanager
-  profiles:
-    active: dev
-  datasource:
-    kafka-manager:
-      jdbc-url: jdbc:mysql://localhost:3306/logi_kafka_manager?characterEncoding=UTF-8&useSSL=false&serverTimezone=GMT%2B8
-      username: root
-      password: 123456
-      driver-class-name: com.mysql.cj.jdbc.Driver
-  main:
-    allow-bean-definition-overriding: true
-
-  servlet:
-    multipart:
-      max-file-size: 100MB
-      max-request-size: 100MB
-
-logging:
-  config: classpath:logback-spring.xml
-
-custom:
-  idc: cn
-  store-metrics-task:
-    community:
-      topic-metrics-enabled: true
-    didi: # 滴滴Kafka特有的指标
-      app-topic-metrics-enabled: false
-      topic-request-time-metrics-enabled: false
-      topic-throttled-metrics-enabled: false
-
-# 任务相关的配置
-task:
-  op:
-    sync-topic-enabled: false                       # 未落盘的Topic定期同步到DB中
-    order-auto-exec:                                # 工单自动化审批线程的开关
-      topic-enabled: false                          # Topic工单自动化审批开关, false:关闭自动化审批, true:开启
-      app-enabled: false                            # App工单自动化审批开关, false:关闭自动化审批, true:开启
-  metrics:
-    collect:                                # 收集指标
-      broker-metrics-enabled: true          # 收集Broker指标
-    sink:                                       # 上报指标
-      cluster-metrics:                          # 上报cluster指标
-        sink-db-enabled: true                   # 上报到db
-      broker-metrics:                           # 上报broker指标
-        sink-db-enabled: true                   # 上报到db
-    delete:                                           # 删除指标
-      delete-limit-size: 1000                         # 单次删除的批大小
-      cluster-metrics-save-days: 14                   # 集群指标保存天数
-      broker-metrics-save-days: 14                    # Broker指标保存天数
-      topic-metrics-save-days: 7                      # Topic指标保存天数
-      topic-request-time-metrics-save-days: 7         # Topic请求耗时指标保存天数
-      topic-throttled-metrics-save-days: 7            # Topic限流指标保存天数
-      app-topic-metrics-save-days: 7                  # App+Topic指标保存天数
-
-thread-pool:
-  collect-metrics:
-    thread-num: 256  # 收集指标线程池大小
-    queue-size: 5000 # 收集指标线程池的queue大小
-  api-call:
-    thread-num: 16   # api服务线程池大小
-    queue-size: 5000 # api服务线程池的queue大小
-
-client-pool:
-  kafka-consumer:
-    min-idle-client-num: 24       # 最小空闲客户端数
-    max-idle-client-num: 24       # 最大空闲客户端数
-    max-total-client-num: 24      # 最大客户端数
-    borrow-timeout-unit-ms: 3000  # 租借超时时间，单位毫秒
-
-account:
-  jump-login:
-    gateway-api: false            # 网关接口
-    third-part-api: false         # 第三方接口
-  ldap:
-    enabled: false
-    url: ldap://127.0.0.1:389/
-    basedn: dc=tsign,dc=cn
-    factory: com.sun.jndi.ldap.LdapCtxFactory
-    filter: sAMAccountName
-    security:
-      authentication: simple
-      principal: cn=admin,dc=tsign,dc=cn
-      credentials: admin
-    auth-user-registration: true
-    auth-user-registration-role: normal
-
-kcm:                                  # 集群安装部署，仅安装broker
-  enabled: false                      # 是否开启
-  s3:                                   # s3 存储服务
-    endpoint: s3.didiyunapi.com
-    access-key: 1234567890
-    secret-key: 0987654321
-    bucket: logi-kafka
-  n9e:                                  # 夜莺
-    base-url: http://127.0.0.1:8004     # 夜莺job服务地址
-    user-token: 12345678                # 用户的token
-    timeout: 300                        # 当台操作的超时时间
-    account: root                       # 操作时使用的账号
-    script-file: kcm_script.sh          # 脚本，已内置好，在源码的kcm模块内，此处配置无需修改
-    logikm-url: http://127.0.0.1:8080   # logikm部署地址，部署时kcm_script.sh会调用logikm检查部署中的一些状态
-
-monitor:
-  enabled: false
-  n9e:
-    nid: 2
-    user-token: 1234567890
-    mon:
-      base-url: http://127.0.0.1:8000 # 夜莺v4版本，默认端口统一调整为了8000
-    sink:
-      base-url: http://127.0.0.1:8000 # 夜莺v4版本，默认端口统一调整为了8000
-    rdb:
-      base-url: http://127.0.0.1:8000 # 夜莺v4版本，默认端口统一调整为了8000
-
-notify:
-  kafka:
-    cluster-id: 95
-    topic-name: didi-kafka-notify
-  order:
-    detail-url: http://127.0.0.1

distribution/conf/logback-spring.xml

-<?xml version="1.0" encoding="UTF-8"?>
-<configuration scan="true" scanPeriod="10 seconds">
-    <contextName>logback</contextName>
-    <property name="log.path" value="./logs" />
-
-    <!-- 彩色日志 -->
-    <!-- 彩色日志依赖的渲染类 -->
-    <conversionRule conversionWord="clr" converterClass="org.springframework.boot.logging.logback.ColorConverter" />
-    <conversionRule conversionWord="wex" converterClass="org.springframework.boot.logging.logback.WhitespaceThrowableProxyConverter" />
-    <conversionRule conversionWord="wEx" converterClass="org.springframework.boot.logging.logback.ExtendedWhitespaceThrowableProxyConverter" />
-    <!-- 彩色日志格式 -->
-    <property name="CONSOLE_LOG_PATTERN" value="${CONSOLE_LOG_PATTERN:-%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){faint} %clr(${LOG_LEVEL_PATTERN:-%5p}) %clr(${PID:- }){magenta} %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %m%n${LOG_EXCEPTION_CONVERSION_WORD:-%wEx}}"/>
-
-    <!--输出到控制台-->
-    <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
-        <filter class="ch.qos.logback.classic.filter.ThresholdFilter">
-            <level>info</level>
-        </filter>
-        <encoder>
-            <Pattern>${CONSOLE_LOG_PATTERN}</Pattern>
-            <charset>UTF-8</charset>
-        </encoder>
-    </appender>
-
-
-    <!--输出到文件-->
-
-    <!-- 时间滚动输出 level为 DEBUG 日志 -->
-    <appender name="DEBUG_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <file>${log.path}/log_debug.log</file>
-        <!--日志文件输出格式-->
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset> <!-- 设置字符集 -->
-        </encoder>
-        <!-- 日志记录器的滚动策略，按日期，按大小记录 -->
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <!-- 日志归档 -->
-            <fileNamePattern>${log.path}/log_debug_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <!--日志文件保留天数-->
-            <maxHistory>7</maxHistory>
-        </rollingPolicy>
-        <!-- 此日志文件只记录debug级别的 -->
-        <filter class="ch.qos.logback.classic.filter.LevelFilter">
-            <level>debug</level>
-            <onMatch>ACCEPT</onMatch>
-            <onMismatch>DENY</onMismatch>
-        </filter>
-    </appender>
-
-    <!-- 时间滚动输出 level为 INFO 日志 -->
-    <appender name="INFO_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <!-- 正在记录的日志文件的路径及文件名 -->
-        <file>${log.path}/log_info.log</file>
-        <!--日志文件输出格式-->
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset>
-        </encoder>
-        <!-- 日志记录器的滚动策略，按日期，按大小记录 -->
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <!-- 每天日志归档路径以及格式 -->
-            <fileNamePattern>${log.path}/log_info_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <!--日志文件保留天数-->
-            <maxHistory>7</maxHistory>
-        </rollingPolicy>
-        <!-- 此日志文件只记录info级别的 -->
-        <filter class="ch.qos.logback.classic.filter.LevelFilter">
-            <level>info</level>
-            <onMatch>ACCEPT</onMatch>
-            <onMismatch>DENY</onMismatch>
-        </filter>
-    </appender>
-
-    <!-- 时间滚动输出 level为 WARN 日志 -->
-    <appender name="WARN_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <!-- 正在记录的日志文件的路径及文件名 -->
-        <file>${log.path}/log_warn.log</file>
-        <!--日志文件输出格式-->
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset> <!-- 此处设置字符集 -->
-        </encoder>
-        <!-- 日志记录器的滚动策略，按日期，按大小记录 -->
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${log.path}/log_warn_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <!--日志文件保留天数-->
-            <maxHistory>7</maxHistory>
-        </rollingPolicy>
-        <!-- 此日志文件只记录warn级别的 -->
-        <filter class="ch.qos.logback.classic.filter.LevelFilter">
-            <level>warn</level>
-            <onMatch>ACCEPT</onMatch>
-            <onMismatch>DENY</onMismatch>
-        </filter>
-    </appender>
-
-
-    <!-- 时间滚动输出 level为 ERROR 日志 -->
-    <appender name="ERROR_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <!-- 正在记录的日志文件的路径及文件名 -->
-        <file>${log.path}/log_error.log</file>
-        <!--日志文件输出格式-->
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset> <!-- 此处设置字符集 -->
-        </encoder>
-        <!-- 日志记录器的滚动策略，按日期，按大小记录 -->
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${log.path}/log_error_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <!--日志文件保留天数-->
-            <maxHistory>7</maxHistory>
-        </rollingPolicy>
-        <!-- 此日志文件只记录ERROR级别的 -->
-        <filter class="ch.qos.logback.classic.filter.LevelFilter">
-            <level>ERROR</level>
-            <onMatch>ACCEPT</onMatch>
-            <onMismatch>DENY</onMismatch>
-        </filter>
-    </appender>
-
-    <!-- Metrics信息收集日志 -->
-    <appender name="COLLECTOR_METRICS_LOGGER" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <file>${log.path}/metrics/collector_metrics.log</file>
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset>
-        </encoder>
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${log.path}/metrics/collector_metrics_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <maxHistory>3</maxHistory>
-        </rollingPolicy>
-    </appender>
-
-    <!-- Metrics信息收集日志 -->
-    <appender name="API_METRICS_LOGGER" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <file>${log.path}/metrics/api_metrics.log</file>
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset>
-        </encoder>
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${log.path}/metrics/api_metrics_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <maxHistory>3</maxHistory>
-        </rollingPolicy>
-    </appender>
-
-    <!-- Metrics信息收集日志 -->
-    <appender name="SCHEDULED_TASK_LOGGER" class="ch.qos.logback.core.rolling.RollingFileAppender">
-        <file>${log.path}/metrics/scheduled_tasks.log</file>
-        <encoder>
-            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{50} - %msg%n</pattern>
-            <charset>UTF-8</charset>
-        </encoder>
-        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
-            <fileNamePattern>${log.path}/metrics/scheduled_tasks_%d{yyyy-MM-dd}.%i.log</fileNamePattern>
-            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
-                <maxFileSize>100MB</maxFileSize>
-            </timeBasedFileNamingAndTriggeringPolicy>
-            <maxHistory>5</maxHistory>
-        </rollingPolicy>
-    </appender>
-
-    <logger name="COLLECTOR_METRICS_LOGGER" level="DEBUG" additivity="false">
-        <appender-ref ref="COLLECTOR_METRICS_LOGGER"/>
-    </logger>
-    <logger name="API_METRICS_LOGGER" level="DEBUG" additivity="false">
-        <appender-ref ref="API_METRICS_LOGGER"/>
-    </logger>
-    <logger name="SCHEDULED_TASK_LOGGER" level="DEBUG" additivity="false">
-        <appender-ref ref="SCHEDULED_TASK_LOGGER"/>
-    </logger>
-
-    <logger name="org.apache.ibatis" level="INFO" additivity="false" />
-    <logger name="org.mybatis.spring" level="INFO" additivity="false" />
-    <logger name="com.github.miemiedev.mybatis.paginator" level="INFO" additivity="false" />
-
-    <root level="info">
-        <appender-ref ref="CONSOLE" />
-        <appender-ref ref="DEBUG_FILE" />
-        <appender-ref ref="INFO_FILE" />
-        <appender-ref ref="WARN_FILE" />
-        <appender-ref ref="ERROR_FILE" />
-        <!--<appender-ref ref="METRICS_LOG" />-->
-    </root>
-
-    <!--生产环境:输出到文件-->
-    <!--<springProfile name="pro">-->
-        <!--<root level="info">-->
-            <!--<appender-ref ref="CONSOLE" />-->
-            <!--<appender-ref ref="DEBUG_FILE" />-->
-            <!--<appender-ref ref="INFO_FILE" />-->
-            <!--<appender-ref ref="ERROR_FILE" />-->
-            <!--<appender-ref ref="WARN_FILE" />-->
-        <!--</root>-->
-    <!--</springProfile>-->
-</configuration>
\ No newline at end of file

distribution/conf/settings.xml

-<settings>
-    <mirrors>
-        <mirror>
-            <id>aliyunmaven</id>
-            <mirrorOf>*</mirrorOf>
-            <name>阿里云公共仓库</name>
-            <url>https://maven.aliyun.com/repository/public</url>
-        </mirror>
-    </mirrors>
-</settings>
\ No newline at end of file

distribution/pom.xml

-<?xml version="1.0" encoding="UTF-8"?>
-
-<project xmlns="http://maven.apache.org/POM/4.0.0"
-         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
-
-    <parent>
-        <artifactId>kafka-manager</artifactId>
-        <groupId>com.xiaojukeji.kafka</groupId>
-        <version>${kafka-manager.revision}</version>
-    </parent>
-
-    <modelVersion>4.0.0</modelVersion>
-
-    <artifactId>distribution</artifactId>
-    <name>distribution</name>
-    <packaging>pom</packaging>
-
-    <dependencies>
-        <dependency>
-            <groupId>${project.groupId}</groupId>
-            <artifactId>kafka-manager-web</artifactId>
-            <version>${kafka-manager.revision}</version>
-        </dependency>
-    </dependencies>
-
-    <profiles>
-
-        <profile>
-            <id>release-kafka-manager</id>
-            <dependencies>
-                <dependency>
-                    <groupId>${project.groupId}</groupId>
-                    <artifactId>kafka-manager-web</artifactId>
-                    <version>${kafka-manager.revision}</version>
-                </dependency>
-            </dependencies>
-            <build>
-                <plugins>
-                    <plugin>
-                        <groupId>org.apache.maven.plugins</groupId>
-                        <artifactId>maven-assembly-plugin</artifactId>
-                        <configuration>
-                            <descriptors>
-                                <descriptor>release-km.xml</descriptor>
-                            </descriptors>
-                            <tarLongFileMode>posix</tarLongFileMode>
-                        </configuration>
-                        <executions>
-                            <execution>
-                                <id>make-assembly</id>
-                                <phase>install</phase>
-                                <goals>
-                                    <goal>single</goal>
-                                </goals>
-                            </execution>
-                        </executions>
-                    </plugin>
-                </plugins>
-                <finalName>kafka-manager</finalName>
-            </build>
-        </profile>
-    </profiles>
-</project>

distribution/readme.md

-## 说明
-
-### 1.创建mysql数据库文件
-> conf/create_mysql_table.sql
-
-### 2. 修改配置文件
-> conf/application.yml.example
-> 请将application.yml.example 复制一份改名为application.yml；
-> 并放在同级目录下(conf/); 并修改成自己的配置
-> 这里的优先级比jar包内配置文件的默认值高; 
-> 
-
-### 3.启动/关闭kafka-manager
-> sh bin/startup.sh    启动
-> 
-> sh shutdown.sh       关闭
-> 
-
-
-### 4.升级jar包
-> 如果是升级, 可以看看文件 `upgrade_config.md` 的配置变更历史;
-> 
\ No newline at end of file

distribution/release-km.xml

-<?xml version="1.0" encoding="UTF-8"?>
-
-<assembly>
-    <id>${project.version}</id>
-    <includeBaseDirectory>true</includeBaseDirectory>
-    <formats>
-        <format>dir</format>
-        <format>tar.gz</format>
-        <format>zip</format>
-    </formats>
-    <fileSets>
-        <fileSet>
-            <includes>
-                <include>conf/**</include>
-            </includes>
-        </fileSet>
-
-        <fileSet>
-            <includes>
-                <include>bin/*</include>
-            </includes>
-            <fileMode>0755</fileMode>
-        </fileSet>
-    </fileSets>
-    <files>
-
-
-        <file>
-            <source>readme.md</source>
-            <destName>readme.md</destName>
-        </file>
-        <file>
-            <source>upgrade_config.md</source>
-            <destName>upgrade_config.md</destName>
-        </file>
-        <file>
-            <!--打好的jar包名称和放置目录-->
-            <source>../kafka-manager-web/target/kafka-manager.jar</source>
-            <outputDirectory>target/</outputDirectory>
-        </file>
-    </files>
-
-    <moduleSets>
-        <moduleSet>
-            <useAllReactorProjects>true</useAllReactorProjects>
-            <includes>
-                <include>com.xiaojukeji.kafka:kafka-manager-web</include>
-            </includes>
-        </moduleSet>
-    </moduleSets>
-</assembly>

distribution/upgrade_config.md

-
-## 版本升级配置变更
-> 本文件 从 V2.2.0 开始记录; 如果配置有变更则会填写到下文中; 如果没有,则表示无变更;
-> 当您从一个很低的版本升级时候,应该依次执行中间有过变更的sql脚本
-
-
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-### 1.升级至`V2.2.0`版本
-
-#### 1.mysql变更
-
-`2.2.0`版本在`cluster`表及`logical_cluster`各增加了一个字段，因此需要执行下面的sql进行字段的增加。
-
-```sql
-# 往cluster表中增加jmx_properties字段, 这个字段会用于存储jmx相关的认证以及配置信息
-ALTER TABLE `cluster` ADD COLUMN `jmx_properties` TEXT NULL COMMENT 'JMX配置' AFTER `security_properties`;
-
-# 往logical_cluster中增加identification字段, 同时数据和原先name数据相同, 最后增加一个唯一键. 
-# 此后, name字段还是表示集群名称, 而identification字段表示的是集群标识, 只能是字母数字及下划线组成, 
-# 数据上报到监控系统时, 集群这个标识采用的字段就是identification字段, 之前使用的是name字段.
-ALTER TABLE `logical_cluster` ADD COLUMN `identification` VARCHAR(192) NOT NULL DEFAULT '' COMMENT '逻辑集群标识' AFTER `name`;
-
-UPDATE `logical_cluster` SET `identification`=`name` WHERE id>=0;
-
-ALTER TABLE `logical_cluster` ADD INDEX `uniq_identification` (`identification` ASC);
-```
-
-### 升级至`2.3.0`版本
-
-#### 1.mysql变更
-`2.3.0`版本在`gateway_config`表增加了一个描述说明的字段，因此需要执行下面的sql进行字段的增加。
-
-```sql
-ALTER TABLE `gateway_config` 
-ADD COLUMN `description` TEXT NULL COMMENT '描述信息' AFTER `version`;
-```
-
-### 升级至`2.6.0`版本
-
-#### 1.mysql变更
-`2.6.0`版本在`account`表增加用户姓名，部门名，邮箱三个字段，因此需要执行下面的sql进行字段的增加。
-
-```sql
-ALTER TABLE `account`
-ADD COLUMN `display_name` VARCHAR(256) NOT NULL DEFAULT '' COMMENT '用户名' AFTER `role`,
-ADD COLUMN `department` VARCHAR(256) NOT NULL DEFAULT '' COMMENT '部门名' AFTER `display_name`,
-ADD COLUMN `mail` VARCHAR(256) NOT NULL DEFAULT '' COMMENT '邮箱' AFTER `department`;
-```

docs/dev_guide/LogiKM单元测试和集成测试.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-
-# LogiKM单元测试和集成测试
-
-## 1、单元测试
-### 1.1 单元测试介绍
-单元测试又称模块测试，是针对软件设计的最小单位——程序模块进行正确性检验的测试工作。
-其目的在于检查每个程序单元能否正确实现详细设计说明中的模块功能、性能、接口和设计约束等要求，
-发现各模块内部可能存在的各种错误。单元测试需要从程序的内部结构出发设计测试用例。
-多个模块可以平行地独立进行单元测试。
-
-### 1.2 LogiKM单元测试思路
-LogiKM单元测试思路主要是测试Service层的方法，通过罗列方法的各种参数，
-判断方法返回的结果是否符合预期。单元测试的基类加了@SpringBootTest注解，即每次运行单测用例都启动容器
-
-### 1.3 LogiKM单元测试注意事项
-1. 单元测试用例在kafka-manager-core以及kafka-manager-extends下的test包中
-2. 配置在resources/application.yml，包括运行单元测试用例启用的数据库配置等等
-3. 编译打包项目时，加上参数-DskipTests可不执行测试用例，例如使用命令行mvn -DskipTests进行打包
-
-
-
-
-## 2、集成测试
-### 2.1 集成测试介绍
-集成测试又称组装测试，是一种黑盒测试。通常在单元测试的基础上，将所有的程序模块进行有序的、递增的测试。
-集成测试是检验程序单元或部件的接口关系，逐步集成为符合概要设计要求的程序部件或整个系统。
-
-### 2.2 LogiKM集成测试思路
-LogiKM集成测试主要思路是对Controller层的接口发送Http请求。
-通过罗列测试用例，模拟用户的操作，对接口发送Http请求，判断结果是否达到预期。
-本地运行集成测试用例时，无需加@SpringBootTest注解（即无需每次运行测试用例都启动容器）
-
-### 2.3 LogiKM集成测试注意事项
-1. 集成测试用例在kafka-manager-web的test包下 
-2. 因为对某些接口发送Http请求需要先登陆，比较麻烦，可以绕过登陆，方法可见教程见docs -> user_guide -> call_api_bypass_login
-3. 集成测试的配置在resources/integrationTest-settings.properties文件下，包括集群地址，zk地址的配置等等
-4. 如果需要运行集成测试用例，需要本地先启动LogiKM项目
-5. 编译打包项目时，加上参数-DskipTests可不执行测试用例，例如使用命令行mvn -DskipTests进行打包
\ No newline at end of file

docs/dev_guide/connect_jmx_failed.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-## JMX-连接失败问题解决
-
-集群正常接入Logi-KafkaManager之后，即可以看到集群的Broker列表，此时如果查看不了Topic的实时流量，或者是Broker的实时流量信息时，那么大概率就是JMX连接的问题了。
-
-下面我们按照步骤来一步一步的检查。
-
-### 1、问题&说明
-
-**类型一：JMX配置未开启**
-
-未开启时，直接到`2、解决方法`查看如何开启即可。
-
-![check_jmx_opened](./assets/connect_jmx_failed/check_jmx_opened.jpg)
-
-
-**类型二：配置错误**
-
-`JMX`端口已经开启的情况下，有的时候开启的配置不正确，此时也会导致出现连接失败的问题。这里大概列举几种原因：
-
-- `JMX`配置错误：见`2、解决方法`。
-- 存在防火墙或者网络限制：网络通的另外一台机器`telnet`试一下看是否可以连接上。
-- 需要进行用户名及密码的认证：见`3、解决方法 —— 认证的JMX`。
-- 当logikm和kafka不在同一台机器上时,kafka的Jmx端口不允许其他机器访问:见`4、解决方法`。
-
-
-错误日志例子：
-```
-# 错误一： 错误提示的是真实的IP，这样的话基本就是JMX配置的有问题了。
-2021-01-27 10:06:20.730 ERROR 50901 --- [ics-Thread-1-62] c.x.k.m.c.utils.jmx.JmxConnectorWrap     : JMX connect exception, host:192.168.0.1 port:9999.
-java.rmi.ConnectException: Connection refused to host: 192.168.0.1; nested exception is: 
-
-
-# 错误二：错误提示的是127.0.0.1这个IP，这个是机器的hostname配置的可能有问题。
-2021-01-27 10:06:20.730 ERROR 50901 --- [ics-Thread-1-62] c.x.k.m.c.utils.jmx.JmxConnectorWrap     : JMX connect exception, host:127.0.0.1 port:9999.
-java.rmi.ConnectException: Connection refused to host: 127.0.0.1;; nested exception is: 
-```
-
-### 2、解决方法
-
-这里仅介绍一下比较通用的解决方式，如若有更好的方式，欢迎大家指导告知一下。
-
-修改`kafka-server-start.sh`文件：
-```
-# 在这个下面增加JMX端口的配置
-if [ "x$KAFKA_HEAP_OPTS" = "x" ]; then
-    export KAFKA_HEAP_OPTS="-Xmx1G -Xms1G"
-    export JMX_PORT=9999  # 增加这个配置, 这里的数值并不一定是要9999
-fi
-```
-
- 
-
-修改`kafka-run-class.sh`文件
-```
-# JMX settings
-if [ -z "$KAFKA_JMX_OPTS" ]; then
-  KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false  -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=${当前机器的IP}"
-fi
-
-# JMX port to use
-if [  $JMX_PORT ]; then
-  KAFKA_JMX_OPTS="$KAFKA_JMX_OPTS -Dcom.sun.management.jmxremote.port=$JMX_PORT -Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT"
-fi
-```
-
-
-### 3、解决方法 —— 认证的JMX
-
-如果您是直接看的这个部分，建议先看一下上一节：`2、解决方法`以确保`JMX`的配置没有问题了。
-
-在JMX的配置等都没有问题的情况下，如果是因为认证的原因导致连接不了的，此时可以使用下面介绍的方法进行解决。
-
-**当前这块后端刚刚开发完成，可能还不够完善，有问题随时沟通。**
-
-`Logi-KafkaManager 2.2.0+`之后的版本后端已经支持`JMX`认证方式的连接，但是还没有界面，此时我们可以往`cluster`表的`jmx_properties`字段写入`JMX`的认证信息。
-
-这个数据是`json`格式的字符串，例子如下所示：
-
-```json
-{
-    "maxConn": 10,           # KM对单台Broker的最大JMX连接数
-    "username": "xxxxx",     # 用户名
-    "password": "xxxx",      # 密码
-    "openSSL": true,         # 开启SSL, true表示开启ssl, false表示关闭
-}
-```
-
- 
-
-SQL的例子：
-```sql
-UPDATE cluster SET jmx_properties='{ "maxConn": 10,	"username": "xxxxx", "password": "xxxx", "openSSL": false }' where id={xxx};
-```
-### 4、解决方法 —— 不允许其他机器访问
-![1971b46243fe1d547063ee55b1505ed](https://user-images.githubusercontent.com/2869938/154413486-f6531946-8c4c-447e-aa2e-b112e5e623d6.png)
-
-该图中的127.0.0.1表明该端口只允许本机访问.
-在cdh中可以点击配置->搜索jmx->寻找broker_java_opts 修改com.sun.management.jmxremote.host和java.rmi.server.hostname为本机ip

docs/dev_guide/drawio/KCM实现原理.drawio

-<mxfile host="65bd71144e">
-    <diagram id="bhaMuW99Q1BzDTtcfRXp" name="Page-1">
-        <mxGraphModel dx="1138" dy="830" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
-            <root>
-                <mxCell id="0"/>
-                <mxCell id="1" parent="0"/>
-                <mxCell id="11" value="待部署Kafka-Broker的机器" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;labelPosition=center;verticalLabelPosition=bottom;align=center;verticalAlign=top;dashed=1;" vertex="1" parent="1">
-                    <mxGeometry x="380" y="240" width="320" height="240" as="geometry"/>
-                </mxCell>
-                <mxCell id="24" value="" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;labelPosition=center;verticalLabelPosition=bottom;align=center;verticalAlign=top;dashed=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="410" y="310" width="260" height="160" as="geometry"/>
-                </mxCell>
-                <mxCell id="6" style="edgeStyle=none;html=1;entryX=0;entryY=0.5;entryDx=0;entryDy=0;" edge="1" parent="1" source="2" target="3">
-                    <mxGeometry relative="1" as="geometry"/>
-                </mxCell>
-                <mxCell id="7" value="调用夜莺接口，&lt;br&gt;创建集群安装部署任务" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="6">
-                    <mxGeometry x="-0.0875" y="1" relative="1" as="geometry">
-                        <mxPoint x="9" y="1" as="offset"/>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="9" style="edgeStyle=none;html=1;" edge="1" parent="1" source="2" target="4">
-                    <mxGeometry relative="1" as="geometry"/>
-                </mxCell>
-                <mxCell id="10" value="通过版本管理，将Kafka的安装包，&lt;br&gt;server配置上传到s3中" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="9">
-                    <mxGeometry x="0.0125" y="2" relative="1" as="geometry">
-                        <mxPoint as="offset"/>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="2" value="LogiKM" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
-                    <mxGeometry x="40" y="100" width="120" height="40" as="geometry"/>
-                </mxCell>
-                <mxCell id="12" style="edgeStyle=none;html=1;exitX=0.5;exitY=1;exitDx=0;exitDy=0;entryX=0.5;entryY=0;entryDx=0;entryDy=0;" edge="1" parent="1" source="3" target="5">
-                    <mxGeometry relative="1" as="geometry"/>
-                </mxCell>
-                <mxCell id="13" value="1、下发任务脚本(kcm_script.sh)；&lt;br&gt;2、下发任务操作命令；" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];" vertex="1" connectable="0" parent="12">
-                    <mxGeometry x="-0.0731" y="2" relative="1" as="geometry">
-                        <mxPoint x="-2" y="-16" as="offset"/>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="3" value="夜莺——任务中心" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#cdeb8b;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="480" y="100" width="120" height="40" as="geometry"/>
-                </mxCell>
-                <mxCell id="4" value="S3" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#ffe6cc;strokeColor=#d79b00;" vertex="1" parent="1">
-                    <mxGeometry x="40" y="310" width="120" height="40" as="geometry"/>
-                </mxCell>
-                <mxCell id="5" value="夜莺——Agent(&lt;font color=&quot;#ff3333&quot;&gt;代理执行kcm_script.sh脚本&lt;/font&gt;)" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#d5e8d4;strokeColor=#82b366;" vertex="1" parent="1">
-                    <mxGeometry x="400" y="260" width="280" height="40" as="geometry"/>
-                </mxCell>
-                <mxCell id="22" style="edgeStyle=orthogonalEdgeStyle;html=1;entryX=1;entryY=0.5;entryDx=0;entryDy=0;fontColor=#FF3333;exitX=0;exitY=0.5;exitDx=0;exitDy=0;" edge="1" parent="1" source="14" target="4">
-                    <mxGeometry relative="1" as="geometry"/>
-                </mxCell>
-                <mxCell id="25" value="下载安装包" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#000000;" vertex="1" connectable="0" parent="22">
-                    <mxGeometry x="0.2226" y="-2" relative="1" as="geometry">
-                        <mxPoint x="27" y="2" as="offset"/>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="14" value="执行kcm_script.sh脚本：下载安装包" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="425" y="320" width="235" height="20" as="geometry"/>
-                </mxCell>
-                <mxCell id="18" value="执行kcm_script.sh脚本：安装" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="425" y="350" width="235" height="20" as="geometry"/>
-                </mxCell>
-                <mxCell id="19" value="执行kcm_script.sh脚本：检查安装结果" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="425" y="380" width="235" height="20" as="geometry"/>
-                </mxCell>
-                <mxCell id="23" style="edgeStyle=orthogonalEdgeStyle;html=1;entryX=0.5;entryY=0;entryDx=0;entryDy=0;fontColor=#FF3333;exitX=1;exitY=0.5;exitDx=0;exitDy=0;" edge="1" parent="1" source="20" target="2">
-                    <mxGeometry relative="1" as="geometry">
-                        <Array as="points">
-                            <mxPoint x="770" y="420"/>
-                            <mxPoint x="770" y="40"/>
-                            <mxPoint x="100" y="40"/>
-                        </Array>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="26" value="检查副本同步状态" style="edgeLabel;html=1;align=center;verticalAlign=middle;resizable=0;points=[];fontColor=#000000;" vertex="1" connectable="0" parent="23">
-                    <mxGeometry x="-0.3344" relative="1" as="geometry">
-                        <mxPoint as="offset"/>
-                    </mxGeometry>
-                </mxCell>
-                <mxCell id="20" value="执行kcm_script.sh脚本：检查副本同步" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="425" y="410" width="235" height="20" as="geometry"/>
-                </mxCell>
-                <mxCell id="21" value="执行kcm_script.sh脚本：结束" style="rounded=0;whiteSpace=wrap;html=1;absoluteArcSize=1;arcSize=14;strokeWidth=1;fillColor=#eeeeee;strokeColor=#36393d;" vertex="1" parent="1">
-                    <mxGeometry x="425" y="440" width="235" height="20" as="geometry"/>
-                </mxCell>
-            </root>
-        </mxGraphModel>
-    </diagram>
-</mxfile>
\ No newline at end of file

docs/dev_guide/dynamic_config_manager.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-# 动态配置管理
-
-## 0、目录
-
-- 1、Topic定时同步任务
-- 2、专家服务——Topic分区热点
-- 3、专家服务——Topic分区不足
-- 4、专家服务——Topic资源治理
-- 5、账单配置
-
-
-## 1、Topic定时同步任务
-
-### 1.1、配置的用途
-`Logi-KafkaManager`在设计上，所有的资源都是挂在应用(app)下面。 如果接入的Kafka集群已经存在Topic了，那么会导致这些Topic不属于任何的应用，从而导致很多管理上的不便。
-
-因此，需要有一个方式将这些无主的Topic挂到某个应用下面。
-
-这里提供了一个配置，会定时自动将集群无主的Topic挂到某个应用下面下面。
-
-### 1.2、相关实现
-
-就是一个定时任务，该任务会定期做同步的工作。具体代码的位置在`com.xiaojukeji.kafka.manager.task.dispatch.op`包下面的`SyncTopic2DB`类。
-
-### 1.3、配置说明
-
-**步骤一：开启该功能**
-
-在application.yml文件中，增加如下配置，已经有该配置的话，直接把false修改为true即可
-```yml
-# 任务相关的开关
-task:
-  op:
-    sync-topic-enabled: true # 无主的Topic定期同步到DB中
-```
-
-**步骤二：配置管理中指定挂在那个应用下面**
-
-配置的位置：
-
-![sync_topic_to_db](./assets/dynamic_config_manager/sync_topic_to_db.jpg)
-
-配置键：`SYNC_TOPIC_2_DB_CONFIG_KEY`
-
-配置值(JSON数组)：
-- clusterId：需要进行定时同步的集群ID
-- defaultAppId：该集群无主的Topic将挂在哪个应用下面
-- addAuthority：是否需要加上权限, 默认是false。因为考虑到这个挂载只是临时的，我们不希望用户使用这个App，同时后续可能移交给真正的所属的应用，因此默认是不加上权限。
-
-**注意，这里的集群ID，或者是应用ID不存在的话，会导致配置不生效。该任务对已经在DB中的Topic不会进行修改**
-```json
-[
-  {
-    "clusterId": 1234567, 
-    "defaultAppId": "ANONYMOUS",
-    "addAuthority": false
-  },
-  {
-    "clusterId": 7654321,
-    "defaultAppId": "ANONYMOUS",
-    "addAuthority": false
-  }
-]
-```
-
----
-
-## 2、专家服务——Topic分区热点
-
-在`Region`所圈定的Broker范围内，某个Topic的Leader数在这些圈定的Broker上分布不均衡时，我们认为该Topic是存在热点的Topic。
-
-备注：单纯的查看Leader数的分布，确实存在一定的局限性，这块欢迎贡献更多的热点定义于代码。
-
-
-Topic分区热点相关的动态配置(页面在运维管控->平台管理->配置管理)：
-
-配置Key：
-```
-REGION_HOT_TOPIC_CONFIG
-```
-
-配置Value：
-```json
-{
-  "maxDisPartitionNum": 2,  # Region内Broker间的leader数差距超过2时，则认为是存在热点的Topic
-  "minTopicBytesInUnitB": 1048576,  # 流量低于该值的Topic不做统计
-  "ignoreClusterIdList": [  # 忽略的集群
-    50
-  ]
-}
-```
-
----
-
-## 3、专家服务——Topic分区不足
-
-总流量除以分区数，超过指定值时，则我们认为存在Topic分区不足。
-
-Topic分区不足相关的动态配置(页面在运维管控->平台管理->配置管理)：
-
-配置Key：
-```
-TOPIC_INSUFFICIENT_PARTITION_CONFIG
-```
-
-配置Value：
-```json
-{
-  "maxBytesInPerPartitionUnitB": 3145728,  # 单分区流量超过该值, 则认为分区不去
-  "minTopicBytesInUnitB": 1048576,  # 流量低于该值的Topic不做统计
-  "ignoreClusterIdList": [  # 忽略的集群
-    50
-  ]
-}
-```
-## 4、专家服务——Topic资源治理
-
-首先，我们认为在一定的时间长度内，Topic的分区offset没有任何变化的Topic，即没有数据写入的Topic，为过期的Topic。
-
-Topic分区不足相关的动态配置(页面在运维管控->平台管理->配置管理)：
-
-配置Key：
-```
-EXPIRED_TOPIC_CONFIG
-```
-
-配置Value：
-```json
-{
-  "minExpiredDay": 30,  #过期时间大于此值才显示,
-  "filterRegex": ".*XXX\\s+", #忽略符合此正则规则的Topic
-  "ignoreClusterIdList": [  # 忽略的集群
-    50
-  ]
-}
-```
-
-## 5、账单配置
-
-Logi-KafkaManager除了作为Kafka运维管控平台之外，实际上还会有一些资源定价相关的功能。
-
-当前定价方式：当月Topic的maxAvgDay天的峰值的均值流量作为Topic的使用额度。使用的额度 * 单价 * 溢价(预留buffer) 就等于当月的费用。
-详细的计算逻辑见：com.xiaojukeji.kafka.manager.task.dispatch.biz.CalKafkaTopicBill; 和 com.xiaojukeji.kafka.manager.task.dispatch.biz.CalTopicStatistics;
-
-这块在计算Topic的费用的配置如下所示：
-
-配置Key：
-```
-KAFKA_TOPIC_BILL_CONFIG
-```
-
-配置Value：
-
-```json
-{ 
-  "maxAvgDay": 10, # 使用额度的计算规则
-  "quotaRatio": 1.5, # 溢价率
-  "priseUnitMB": 100 # 单价，即单MB/s流量多少钱
-}
-```

docs/dev_guide/gateway_config_manager.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-# Kafka-Gateway 配置说明
\ No newline at end of file

docs/dev_guide/monitor_system_integrate_with_n9e.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-# 监控系统集成——夜莺
-
-- `Kafka-Manager`通过将 监控的数据 以及 监控的规则 都提交给夜莺，然后依赖夜莺的监控系统从而实现监控告警功能。
-
-- 监控数据上报 & 告警规则的创建等能力已经具备。但类似查看告警历史，告警触发时的监控数据等正在集成中(暂时可以到夜莺系统进行查看)，欢迎有兴趣的同学进行共建 或 贡献代码。
-
-## 1、配置说明
-
-```yml
-# 配置文件中关于监控部分的配置
-monitor:
-  enabled: false
-  n9e:
-    nid: 2
-    user-token: 123456
-    # 夜莺 mon监控服务 地址
-    mon:
-      base-url: http://127.0.0.1:8006
-    # 夜莺 transfer上传服务 地址
-    sink:
-      base-url: http://127.0.0.1:8008
-    # 夜莺 rdb资源服务 地址
-    rdb:
-      base-url: http://127.0.0.1:80
-
-# enabled: 表示是否开启监控告警的功能, true: 开启, false: 不开启
-# n9e.nid: 夜莺的节点ID
-# n9e.user-token: 用户的密钥，在夜莺的个人设置中
-# n9e.mon.base-url: 监控地址
-# n9e.sink.base-url: 数据上报地址
-# n9e.rdb.base-url: 用户资源中心地址
-```
-

docs/dev_guide/monitor_system_integrate_with_self.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-# 监控系统集成
-
-- 监控系统默认与 [夜莺] (https://github.com/didi/nightingale) 进行集成；
-- 对接自有的监控系统需要进行简单的二次开发，即实现部分监控告警模块的相关接口即可；
-- 集成会有两块内容，一个是指标数据上报的集成，还有一个是监控告警规则的集成；
-
-## 1、指标数据上报集成
-
-仅完成这一步的集成之后，即可将监控数据上报到监控系统中，此时已能够在自己的监控系统进行监控告警规则的配置了。
-
-**步骤一：实现指标上报的接口**
-
-- 按照自己内部监控系统的数据格式要求，将数据进行组装成符合自己内部监控系统要求的数据进行上报，具体的可以参考夜莺集成的实现代码。
-- 至于会上报哪些指标，可以查看有哪些地方调用了该接口。
-
-![sink_metrics](./assets/monitor_system_integrate_with_self/sink_metrics.jpg)
-
-**步骤二：相关配置修改**
-
-![change_config](./assets/monitor_system_integrate_with_self/change_config.jpg)
-
-**步骤三：开启上报任务**
-
-![open_sink_schedule](./assets/monitor_system_integrate_with_self/open_sink_schedule.jpg)
-
-
-## 2、监控告警规则集成
-
-完成**1、指标数据上报集成**之后，即可在自己的监控系统进行监控告警规则的配置了。完成该步骤的集成之后，可以在`Logi-KafkaManager`中进行监控告警规则的增删改查等等。
-
-大体上和**1、指标数据上报集成**一致，
-
-**步骤一：实现相关接口**
-
-![integrate_ms](./assets/monitor_system_integrate_with_self/integrate_ms.jpg)
-
-实现完成步骤一之后，接下来的步骤和**1、指标数据上报集成**中的步骤二、步骤三一致，都需要进行相关配置的修改即可。
-
-
-## 3、总结
-
-简单介绍了一下监控告警的集成，嫌麻烦的同学可以仅做 **1、指标数据上报集成** 这一节的内容即可满足一定场景下的需求。
-
-
-**集成过程中，有任何觉得文档没有说清楚的地方或者建议，欢迎入群交流，也欢迎贡献代码，觉得好也辛苦给个star。**

docs/dev_guide/use_mysql_8.md

-
----
-
-![kafka-manager-logo](../assets/images/common/logo_name.png)
-
-**一站式`Apache Kafka`集群指标监控与运维管控平台**
-
---- 
-
-# 使用`MySQL 8`
-
-感谢 [herry-hu](https://github.com/herry-hu) 提供的方案。
-
-
-当前因为无法同时兼容`MySQL 8`与`MySQL 5.7`，因此代码中默认的版本还是`MySQL 5.7`。
-
-
-当前如需使用`MySQL 8`，则需按照下述流程进行简单修改代码。
-
-
-- Step1. 修改application.yml中的MySQL驱动类
-```shell
-
-# 将driver-class-name后面的驱动类修改为:
-# driver-class-name: com.mysql.jdbc.Driver
-driver-class-name: com.mysql.cj.jdbc.Driver
-```
-
-
-- Step2. 修改MySQL依赖包
-```shell
-# 将根目录下面的pom.xml文件依赖的`MySQL`依赖包版本调整为
-
-<dependency>
-    <groupId>mysql</groupId>
-    <artifactId>mysql-connector-java</artifactId>
-#    <version>5.1.41</version>
-    <version>8.0.20</version>
-</dependency>
-```
-

docs/dev_guide/免登录调用接口.md

+
+![Logo](../assets/KnowStreamingLogo.png)
+
+## 登录绕过
+
+### 背景
+
+现在除了开放出来的第三方接口，其他接口都需要走登录认证。
+
+但是第三方接口不多，开放出来的能力有限，但是登录的接口又需要登录，非常的麻烦。
+
+因此，新增了一个登录绕过的功能，为一些紧急临时的需求，提供一个调用不需要登录的能力。
+
+### 使用方式
+
+步骤一：接口调用时，在header中，增加如下信息：
+```shell
+# 表示开启登录绕过
+Trick-Login-Switch : on
+
+# 登录绕过的用户, 这里可以是admin, 或者是其他的, 但是必须在运维管控->平台管理->用户管理中设置了该用户。
+Trick-Login-User : admin
+```
+
+ 
+
+步骤二：在运维管控->平台管理->平台配置上，设置允许了该用户以绕过的方式登录
+```shell
+# 设置的key，必须是这个
+SECURITY.TRICK_USERS
+
+# 设置的value，是json数组的格式，例如
+[ "admin", "logi"]
+```
+
+ 
+
+步骤三：解释说明
+
+设置完成上面两步之后，就可以直接调用需要登录的接口了。
+
+但是还有一点需要注意，绕过的用户仅能调用他有权限的接口，比如一个普通用户，那么他就只能调用普通的接口，不能去调用运维人员的接口。
+