allinurl
Add Virtual Hosts column to "Requested Files"
It's very confusing to me to see multiple requests to / in the Requested Files-table, delivering different content, because / is available on multiple Virtual Hosts.
I would prefer a Virtual Hosts-column on Requested Files or another way to split these requests up.
You can prepend the vhost to the requested files. Please take a look at the man page, Virtual Hosts examples at the bottom of the page.
The output would look like:
Yeah, I already found that option in an issue, but i don't really like the view (vhost + request in one column) of that and think splitting it up would be a more readable solution.
I can look into the new column. However, for the current output, and if it's just a spacing issue, you can just add x amount of spaces between the two awk fields, e.g., '$8=$1" "$8'.
Also it seems that appending the hostname with awk disables the real-time preview, right?. In that case, creating a column for %v could solve this issue.
@allinurl I just bumped into the same problem, and then found this issue. I was just wondering, whether this is still on the roadmap?
Yeah in general most of the panels would be super helpful to have virtual host as a separate column. In particular
- Requested files
- Static requests
- Not found URLs
For most of the other panels I think the filtering that is currently planned (as part of #117) Is enough. Even though a groupBy for the other panels rather then filtering could be super helpful if I want to see a quick health check e.g. which of my vhosts throws the most 5xx errors etc.
@fkrauthan I agree that #117 should make it possible to say, for example, "show me all the 500x errors for this vhost." At the same time, I understand the value in being able to view data for a specific vhost while displaying multiple vhosts on the dashboard. Adding the virtual host in those three panels makes sense, especially when you want to compare several vhosts in a single view. Maybe it could be added as an optional column, hidden by default?
That said, there's also the challenge of how to report it. I assume a single vhost can have multiple METHOD/URI/PROTOCOL combinations, which could result in a long list of entries for just one vhost. Thoughts?
I guess the real question is how valuable is it to not co-relate the information with vHost in particular. /home for wordpress has a completely different meaning to me as /home of my personal website for example. So I think showing more lines is not the end of the world. Especially with filters mixed in this should be even less an issue.