[BUG] sentinel dashboard 1.8.6 cannot register

[silent-night-no-trace]

Issue Description

Type: bug report

Describe what happened

application can not register sentinel dashboard 1.8.6

Describe what you expected to happen

application can register sentinel dashboard 1.8.6

https://github.com/alibaba/Sentinel/wiki/FAQ#q-sentinel-%E6%8E%A7%E5%88%B6%E5%8F%B0%E6%B2%A1%E6%9C%89%E6%98%BE%E7%A4%BA%E6%88%91%E7%9A%84%E5%BA%94%E7%94%A8%E6%88%96%E8%80%85%E6%B2%A1%E6%9C%89%E7%9B%91%E6%8E%A7%E5%B1%95%E7%A4%BA%E5%A6%82%E4%BD%95%E6%8E%92%E6%9F%A5

客户端启动时添加相应的 JVM 参数，包括： 应用名称：-Dproject.name=xxxx（会显示在控制台） 控制台地址：-Dcsp.sentinel.dashboard.server=ip:port 本地的 Sentinel 客户端端口：-Dcsp.sentinel.api.port=xxxx（可选，默认是 8719，有冲突会尝试向后探测） 详细参数配置详情请参考 Sentinel 控制台文档。 启动控制台，运行应用，当 首次访问对应的资源后，等待一段时间 即可在控制台上看到对应的应用以及相应的监控信息。可以通过 curl http://ip:port/tree 命令查看调用链，正常情况下会显示出已访问资源的调用链。

Seen from this document, you must configure the application the JVM parameter Such as CSP, sentinel. Dashboard. Server and so on The app can only be registered However, it is possible to register without specifying it in the sentinel dashboard 1.8.5 release

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

springboot 2.6 spring cloud alibaba 2021.0.5.0 springcloud 2021.0.5

Anything else we need to know?

spring cloud alibaba 2.2.9.RELEASE springcloud Hoxton.SR12 springboot 2.3.12

I was able to register with this environment without adding jvm parameters. I also found a strange problem. I in spring cloud alibaba 2.2.9. RELEASE version setinel automatic assembly on class SentinelAutoConfiguration than application configuration class sentinelConfig priority to load however Spring cloud alibaba 2021.0.5.0 version on the application on the configuration of the class sentinelConfig than setinel automatic SentinelAutoConfiguration priority loading assembly Is this something that's been changed

[silent-night-no-trace]

The source code is analyzed at the following address https://blog.csdn.net/a15835774652/article/details/132234943

Hope to get official help

[silent-night-no-trace]

Can you help me look at this problem? This question has puzzled us for a long time

[silent-night-no-trace]

The same problem occurs when traffic limiting rules cannot be successfully obtained in the dashboard

The source code is analyzed at the following address https://blog.csdn.net/a15835774652/article/details/132469542

[TianMing2018]

try to set spring.cloud.sentinel.eager to true,

earlier initialize heart-beat when the spring container starts when the transport dependency is on classpath, the configuration is effective.

[lihuagang03]

try to set spring.cloud.sentinel.eager to true,

earlier initialize heart-beat when the spring container starts when the transport dependency is on classpath, the configuration is effective.

If you enable this config to init early, the flow control rules have not effective at the first phase of requests.