-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
bugA general bugA general bugregistry: statsdA StatsD Registry related issueA StatsD Registry related issue
Milestone
Description
Environment : spring-boot 2.2.0.RELEASE
micrometer-registry-statsd : 1.3.0 also tried with older versions
steps to replicate the issue:
- Once the application is started statsd metrics will be start pumping to stats daemon running on 8125 udp port
- invoke StatsdMeterRegistry.stop() --> which will shutdown the udp client
- invoke StatsdMeterRegistry.start() --> which will start the udp client. debug mode we can see that udp client status is started
But statsd metrics will not be send.
could you please help to understand the issue. Or is this the right way to reinitialise the connection
Background of the issue : we are using a stasd daemon with a dns name, if the deamon is restarted the ip address maybe different, because of the dns caching udp client will not be able to connect to the stasd daemon if the ip address is different.
We have tried setting networkaddress.cache.ttl=10 but it is not getting affected for the StatsdMeterRegistry UdpClient object
orsigiorgio
Metadata
Metadata
Assignees
Labels
bugA general bugA general bugregistry: statsdA StatsD Registry related issueA StatsD Registry related issue