Separate the code for indicator monitoring #14106
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
[Task] Separate the code for indicator monitoring #14016
Brief changelog
1、Refer to Spring Event Multicaster, improve Dubbo Event Multicaster, and migrate to dubbo-common package.
2、Replace the MetricsEvent that occur in Dubbo with DubboEvent and broadcast them through Dubbo Event Multicaster. Remove the dependence on dubbo-metrics and only retain the dependence on dubbo-metrics-api. Please note that dubbo-plugin and dubbo-spring-boot still retain a dependency on dubbo-metrics-default because they require some advanced capabilities.
3、Split Collector and CollectorEventListener, and convert DubboEvent into MetricsEvent in CollectorEventListener.
4、Add the dubbo-metrics-starter package to listen to DubboEvent and initialize the metrics service at the appropriate time. Merge dubbo-metrics-event and dubbo-metrics-api into dubbo-metrics-core package, and only keep necessary interfaces and annotations in dubbo-metrics-api.
Verifying this change
Submitted DubboEventTest to test dubbo Dubbo Event Multicaster.
Passed all unit tests.