Monitoring: support to change file persistence

[qiffang]

Signed-off-by: qiffang [email protected]
Function
Update logic:

• Init shell copy rule files to $PROM_PATH/rules and then copy and overwrite files in $PERSISTENT_PATH/$TIDB_VERSION to $PROM_PATH/rules

• Reload receive 2 new arguments: root store path (Persistent path) and sub store path(TIDB Version)

• Reload will create/overwrite updated files to $PERSISTENT_PATH/$TIDB_VERSION

Test

• Upgrade values and keep the TIDB version, the changed files is persistent
• Upgrade TIDB Version, updated rules is loss

[tennix]

The datasource files are json format, but the filename suffix is .yaml. This is confusing.

[qiffang]

The datasource files are json format, but the filename suffix is .yaml. This is confusing.

json postfix is invalid. And the file is from tidb-operator, do you think we need to update files to yaml format?

[tennix]

Oh, tidb-operator uses json format but mount it as yaml file. That way I think we should fix it in tidb-operator, and keep this consistent with tidb-operator.

[qiffang]

Oh, tidb-operator uses json format but mount it as yaml file. That way I think we should fix it in tidb-operator, and keep this consistent with tidb-operator.

I will also update yaml format for these files in this PR.

[qiffang]

Oh, tidb-operator uses json format but mount it as yaml file. That way I think we should fix it in tidb-operator, and keep this consistent with tidb-operator.

Using yaml format to replace json format

[tennix]

LGTM