Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow %h (or a new format specifier) to accept looked-up hostnames #1552

Open
zaitseff opened this issue Sep 21, 2019 · 1 comment
Open

Allow %h (or a new format specifier) to accept looked-up hostnames #1552

zaitseff opened this issue Sep 21, 2019 · 1 comment

Comments

@zaitseff
Copy link

@zaitseff zaitseff commented Sep 21, 2019

First off, thank you for writing GoAccess and releasing it!

Could you please implement the ability to have %h (or perhaps a new format specifier like %H) accept hostnames that have already been looked up. In other words, to be able to accept log files where IP addresses are not recorded but the looked-up names are:

crawl-66-249-65-222.googlebot.com - - [21/Sep/2019:09:00:06 +1000] "GET /robots.txt HTTP/1.1" 200 571 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

When I run goaccess with such log files, it complains with something like:

Parsed 10 lines producing the following errors:

Token 'crawl32.bl.semrush.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token 'msnbot-207-46-13-178.search.msn.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'
Token '141-8-143-196.spider.yandex.com' doesn't match specifier '%h'

Format Errors - Verify your log/date/time format

(I tried to search whether someone had already filed this issue, but could not find anything to match).

Thanks!

@allinurl

This comment has been minimized.

Copy link
Owner

@allinurl allinurl commented Sep 23, 2019

I can look into this, however, as a workaround, you could try building from development and pass --no-ip-validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.