nebula 版本：v1.2.0
部署方式（分布式 ）：
是否为线上版本：Y
硬件信息
服务器：30台
磁盘: 8块SSD硬盘。
CPU: 24core,Intel® Xeon® CPU E5-2630 v2 @ 2.60GHz
内存：128G
问题的具体描述
生产环境，vesoft/nebula-stats-exporter:v0.0.1 监控会偶尔出现断点无监控数据的现象，重启nebula-stats-exporter容器后，数据可正常接收，请问如何解决？
相关的 日志信息如下：
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
time="2021-06-11T07:10:06Z" level=error msg="error encoding and sending metric family: write tcp 172.17.0.4:9100->172.17.0.1:49518: write: broken pipe\n" source="log.go:181"
2021/06/11 07:10:06 http: superfluous response.WriteHeader call from github.com/prometheus/client_golang/prometheus/promhttp.(*responseWriterDelegator).WriteHeader (delegator.go:58)
