New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add MySQL audit rule #203

Closed

sjjian opened this issue Jan 11, 2022 · 1 comment

Assignees

Labels

feature verified

Milestone

Member

sjjian commented Jan 11, 2022 •

edited by HuangWeiCen

Loading

新增规则列表

规则	提示	默认提示等级	需求备注	对应PR
检查DDL创建的新索引对应字段是否已存在过多索引	字段xxx上的索引数量过多(%v)	warn	检查某字段上是否存在过多的索引	#233
检查DDL操作的表是否超过指定数据量	DDL操作的表数据量超过 XXX	warn	数据量的判断可参考现有 online DDL 规则的计算方式	#217
检查DML操作的表是否超过指定数据量	DML操作的表数据量超过XXX	warn	数据量的判断可参考现有 online DDL 规则的计算方式	#223
使用explain加强预检查能力	预检查失败：xxxx报错信息	warn	目前SQLE具备基础的库表检查，即SQLE的CheckInvalid方法，会检查DDL库表结构，DML涉及的库表结构，但是DML不会检查字段还有where条件，因此采用explain进行判断，仅当所有语句都是DML时检查	#230

现有规则调整

规则	默认提示等级	需求备注	是否完成
建议选择可选性超过阈值字段作为索引	保持现有一致	索引效率检测,调整1：修改页面审核建议提示为具体的索引未超过可选择性的阈值，例如：索引 idx1(a1), idx2(a2) 未超过可选择性阈值70，不建议选为索引；调整2：该规则分类放到索引优化下	#213
开启索引优化	保持现有一致	名称调整为 '索引创建建议'	#214

sjjian added the feature label

sjjian added this to the v1.2201.0 milestone

sjjian assigned HuangWeiCen

This was referenced Jan 18, 2022

update DDLCheckIndexOption #213

Merged

update ConfigOptimizeIndexEnabled #214

Merged

check DDL Table Size #217

Merged

Check dml result line #223

Merged

CheckInvalid() add explain check #229

Closed

Add explain check #230

Merged

check index too many #233

Merged

HuangWeiCen closed this as completed

Marcus9530 added the verified label

This was referenced Jan 25, 2022

Adjust pre check error #255

Closed

Optimized code #256

Merged

Member Author

sjjian commented Jan 25, 2022

@Marcus9530 预检查未正确提示的问题已修复

This was referenced Jan 26, 2022

Closed

Merged

taolx0 pushed a commit that referenced this issue


          Merge pull request #203 from actiontech/spelling

1fb4443

spelling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment