goaccess
goaccess copied to clipboard
Panels for 403 and 5xx codes in the report
Hi,
Besides 404s, the other specific codes I always check when I look at my access logs are 403s (Forbidden) and the 5xx series (Server error). They are currently present in a summary panel, but it would be great to see the individual info for these occurrences, as they provide a good insight to possible security and server performance issues. Would it be possible to add panels for these categories in the final report similar to the 404 panel? (either as default or as an option).
Thanks, Claudio
Great question. What info are you looking to see for each status code and how should it be displayed? Thanks.
For both for 403 and 5XX codes, I'd like to see the following info:
- Hits
- URL
- Browser/crawler (important specially for the Crawler section, which would point to any URLs requested by search engines being 403-blocked, a big no-no.)
- Country (optional)
I believe the following are not very important:
- Size/Bandwidth, because the content provided is pretty much standard error page content, doesn't vary much.
- Visitors, as their number would probably be 0 just like in the 404s panel.
- Protocol, I just don't have much use for this. (But it may be relevant to other users though)
Hi @allinurl
I am also looking for same enhancement. May I know when you are planning to release this new feature.
Thanks!!! Ananth Francis.
@ananthfrancis This would be part of #1202 which will give you the ability to add custom panels, I still need to get to the on-disk storage before I can work on this, so there will probably be a couple of new releases before I get to this. If you need a workaround, this may help (parses 3xx and 5xx):
# tail -f -n +0 access.log | awk '$9~/3[0-9]{2}|5[0-9]{2}/' | goaccess -o out.html -
@allinurl any update on this?
@finalhit Haven't got to this. Will bump it on the to-do list.
@allinurl Any ETA?
This will be part of #117 as it should be a matter of filtering by any of those statuses and all panels will be updated accordingly. As far as ETA, I'm working on this as we speak. Early tests are already working as they should, working on the details of it. Stay tuned!
Thx allinurl great job Im looking forward to this feature too
@allinurl Any update on this?
@akash-rp Currently working on #117, which should address this feature. Stay tuned!