Support adding prefix to Dubbo service resource name in Sentinel Dubbo Adapter

[zhongxunking]

Dubbo适配器提供的资源名目前没有前缀，只是包路径+类名。导致在控制台看到时不能直观的看出是Dubbo调用。可否增加前缀以示区别。比如服务提供者使用dubbo-provider，服务消费者使用dubbo-consumer

[sentinel-bot]

Hi @zhongxunking, we detect non-English characters in the issue. This comment is an auto translation from @sentinel-bot to help other users to understand this issue.
We encourage you to describe your issue in English which is more friendly to other users.

The resource name provided by the Dubbo adapter adds the Dubbo prefix.

The resource name provided by the Dubbo adapter currently has no prefix, just the package path + class name. It is not intuitive to see that the Dubbo call is made when you see it in the console. Can I add a prefix to show the difference. For example, the service provider uses dubbo-provider, and the service consumer uses dubbo-consumer.

[sczyh30]

Hi, thanks for your suggestion. For this, we need to consider compatibility with previous versions. Maybe we can add a property to control whether the resource name has a common prefix and configure the common prefix.

[zhongxunking]

thanks, it is good. which version of sentinel will provide the feature?

[sczyh30]

Contribution is welcomed~

[linlinisme]

I have a question: If the dubbo service shows the prefix, then the configuration rules should be prefixed?

[sczyh30]

I have a question: If the dubbo service shows the prefix, then the configuration rules should be prefixed?

If the Dubbo service resource is added with the prefix, then when we configure rules it should also be prefixed. This is not compatible with existing rules.

[linlinisme]

So is it necessary to add the prefix?

[sczyh30]

thanks, it is good. which version of sentinel will provide the feature?

This will be introduced in 1.7.0. See #859 for details.