micrometer-metrics/micrometer
StatsdMeterRegistry doesn't renew resolved ip address on DNS change
Offen
#1.252 geöffnet am 27.02.2019
enhancementhelp wantedregistry: statsd
Repository-Metriken
- Stars
- (4.881 Sterne)
- PR-Merge-Metriken
- (PR-Metriken ausstehend)
Beschreibung
Hello everyone.
I've faced with the problem that StatsdMeterRegistry doesn't aware of DNS changes after it was start()ed.
As a result, metrics aren't delivered to Telegraf and there is no warning or so in logs.
How to reproduce:
- Create record in /etc/hosts file, e.g.:
127.0.0.1 telegraf.kube-system.svc.cluster.local. - Start application with StatsdMeterRegistry enabled and use host described above.
- Change record in /etc/hosts file to another ip (
127.0.0.2for example)
Actual result: Using wireshark/tcpdump you can see that all metrics are being sent to 127.0.0.1 even after step 3.
Expected result: StatsdMeterRegistry respect DNS name change.
Can be reproduced on real network/DNS server. Security manager disabled. Micrometer version: 1.1.3, reproducible on 1.0.7 as well.