"Perhaps stating your overall objective would be handy here to get more appropriate feedback"

Hmm... judging by your answer; I do indeed need to better define my objective -- Sorry. :-(

What I'm hoping to ultimately achieve, is to have the current logging the HTTPd provides, return (resolve) the connecting IP addresses it currently dumps to the log(s). Maybe an example would be prudent here:

66.249.69.38 my.web.host - [12/Jun/2018:12:32:26 -0700] "GET / HTTP/1.
+1" 200 3306 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKi
+t/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36"
[download]

When what I'd really like to see, is the following:

crawl-66-249-69-38.googlebot.com my.web.host - [12/Jun/2018:12:32:26 -
+0700] "GET / HTTP/1.1" 200 3306 "-" "Mozilla/5.0 (Windows NT 10.0; Wi
+n64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100
+ Safari/537.36"
[download]

Seems that this should be possible. I could simply:

#!/bin/sh -

cat /var/log/my.web.host-access-log | awk '{ print $1; }' | ...
[download]

or some such to feed the logs to a resolver. But I'm ideally looking for a way to process the log(s) (connections) in "real time". So that the logs have the correct access times. I can imagine filtering , or piping it. But am not sure if they're the only/best solutions. So here I ask. :-)

Thanks, stevieb, for taking the time to respond!