We are using Metricbeat to collect info on our RabbitMQ cluster. With a DNS change we cutover our cluster, but the monitoring itself kept reporting on the cluster with the old IP address. A restart of the monitoring updated everything to correct addresses, we are just wondering if this is a known issue, or if there is an option for updating / turning-off this IP address caching?
Beats don't cache DNS results. The caching normally happens somewhere else. On Windows/macOS it is the OS itself that caches lookups. On Linux it depends on your
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.