3 ms·
> What is a legitimate reason for a logging library to make network requests based on the contents of what is being logged I encountered a similar problem rece
by est 5y ago
> What is a legitimate reason for a logging library to make network requests based on the contents of what is being logged
I encountered a similar problem recently, my own logger can get the current container/pod IP address, it's painful to tell which host from the IPs in logs, so I had to do a manual DNS lookup to include a hostname instead. I was hoping the logger could automatically do a lookup and cache it for me.
- suraci 5y agoWhy didn't write logs to stdout and scrape container log files by fluentbit/promtail/etc? I'm working on logging infrastructure now and really want to know the reason behind this(before I built it...)
- est 5y agoI do, but with a different log aggregator (vector.dev), there are three reasons: 1. the log aggregator doesn't exactly support DNS lookups 2. You have to parse the log first, exactly precisely where the IP part, then do a proper lookup. But sometimes the log is just a mess. 3. where the log aggregator located cannot do host lookup because of different network and different DNS server. So overall the lookup would better be done locally.
- Too 5y agoPretty sure the original rationale for this clusterfuck must have been something similar: “we only have user id here, but want the logs to contain user name”. Send this requirement to the cheapest bidder and here we are.