Gerardo O.

@gitanupam while this is implemented, grep or any other filtering tool would be your friend here. e.g., For **real-time filtering**: # tail -f -n +0 access.log | grep --line-buffered '192.168.3.1'...

@Shagon94 certainly still on top of the list. however, there's an outstanding issue with the on-disk storage that needs to be worked on before this. stay tuned though.

@dmaziuk agree on that. Stay tuned for the upcoming storage change.

@nkvname need to finish the on-disk storage replacement, this is second on the list though.

@domolicious I agree, this would be of great value! Issue **#1274** Stay tuned!

@insidesmart This issue will add that feature, it won't be part of the upcoming release (v1.4). I've addressed the storage issue mentioned before, so after deploying 1.4 I can focus...

@air3ijai This is being implemented so that it works against currently parsed logs. This feature won't be enabled if a dataset was persisted and the log doesn't exist anymore.

Folks, I just wanted to give a positive and early update on this. I'm working on it as we speak. Early tests are already working as they should, though, still...

Please try: --ignore-referer= - Ignore a referer from being counted. Wild cards are allowed. i.e., *.bing.com

This should do it, let me know: goaccess access.log --log-format='%dT%t+%^ | %h | %e | %m %U %H | %s | %b | %R | %u| %T | %^ |...