ZhengBing520 opened a new issue, #11311: URL: https://github.com/apache/skywalking/issues/11311
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened Starting OAP, it was found that the custom alarm rules did not take effect, and during debugging, it was found that they were overwritten by resource/alarm settings. yml; The reasons are as follows: 1. When BootstrapFlow#notifyAfterCompleted starts, the ConfigmapConfigurationProvider starts before the AlarmModuleProvider 2. When the FetchingConfigWatcherRegister#start method is started, alarm rules will be initialized 3. When the AlarmModuleProvider#notifyAfterCompleted method is started, the AlarmRulesWatcher#notify method is called, but the settingsString remains unchanged 4. The next time the FetchingConfigWatcherRegister#configSync method is called, the alarm rules will not be updated ### What you expected to happen If there are custom rules and they have already been initialized, alarm-settings.yml should not be overwritten ### How to reproduce 1. add env SW_CONFIGURATION=k8s-configmap, KUBECONFIG='path/kube.conf' 2. run OAPServerStartUp.java ### Anything else org.apache.skywalking.oap.server.library.module.BootstrapFlow#notifyAfterCompleted <img width="396" alt="d28f7adb49cc4aefce722edcb6d2f466" src="https://github.com/apache/skywalking/assets/32810704/f42c3f29-d539-4383-b310-d9f34ba3da5c";> ### Are you willing to submit a pull request to fix on your own? - [X] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
