Sentinel dashboard fetch metric failed: ConnectionException

[tonfay]

控制台无法正常监控，机器列表里面健康状态正常，但是没有监控数据。

实现类:
TransportConfig.getHeartbeatClientIp()->HostNameUtil.resolveHost()
两种实现方式:
1.修改对应hostname与ip地址的映射关系即可
2.可指定-Dcsp.sentinel.heartbeat.client.ip=xxx 配置

[sentinel-bot]

Hi @tonfay, 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.

/metric ConnectionException

The console could not be monitored properly, the health status of the machine list was normal, but there was no monitoring data.

Implementation class:
TransportConfig.getHeartbeatClientIp()->HostNameUtil.resolveHost()
Two ways to achieve:

1. Modify the mapping relationship between the corresponding hostname and ip address.
2. You can specify -Dcsp.sentinel.heartbeat.client.ip=xxx configuration

[sczyh30]

Thanks for summarizing. I've added this item to FAQ :)

[Liu1796997299]

For this question:The console could not be monitored properly, the health status of the machine list was normal, but there was no monitoring data.And the Sentinel application had ran on CentOS and throws this exception:

For ".yml" or ".properties",add this configuration property about "spring.cloud.sentinel.transport.clientIp".And the value is your Sentinel Controller's address.I test it myself,and pass!