Open loganmc10 opened 3 years ago
@loganmc10, why was this closed? Was this implemented? I'm interested on this too.
My org just stopped doing DNS resolution in Telegraf, we just rely on the IPs for now, so it wasn't something we needed anymore, but I agree it would be useful. I'll re-open it since I know there are others looking for it
Feature Request
@ssoroka
Proposal:
Currently, the reverse DNS processor only caches successful lookups. It should also cache failed lookups for a period of time
Current behavior:
Only successful lookups are cached
Desired behavior:
Failed lookups would also be cached so that it doesn't constantly try to lookup the same IP
Use case:
If a device sends a large amount of data to Telegraf, but the IP doesn't resolve using reverse lookup, Telegraf will try to resolve that IP every time a new message comes in. It should remember that it failed and only retry after a defined period of time.