micrometer: StatsdMeterRegistry doesn't renew resolved ip address on DNS change

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:

  1. Create record in /etc/hosts file, e.g.: 127.0.0.1 telegraf.kube-system.svc.cluster.local.
  2. Start application with StatsdMeterRegistry enabled and use host described above.
  3. Change record in /etc/hosts file to another ip (127.0.0.2 for 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.

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Reactions: 2
  • Comments: 15 (8 by maintainers)

Most upvoted comments

So we can close this in favour of #3563 (comment) ?

Maybe the opposite, close #3563 and keep this open.