I suppose this is does by design so I filed it as a feature request but don't hesitate to change it if it's a bug.
I did a quick test with another browser so that I'm anonymous and realized that between pages /node was accessed/hit, this is most likely due to the fact that drupal in it's base take the path as an arguments to the /node page however I'm not concerned about the basic page progression but about the user actions so that the pages that is referred to and from node are directly referred to each other. In the attached example, /content/account-advantages would refer to /content/neverwinter-nights-2-toolset-autosave-failed-recovery, which would be referred to by the former. If for some reason it's better to log it this way, there could be two different views in the Recent hits : the original one and another that skip "/node" by linking the items that passed through it.
In the following example, the Details pages are listed in order from the Recent hits page top to bottom (chronologically inverted).
| Comment | File | Size | Author |
|---|---|---|---|
| drupal-statistics_advanced-Details03.png | 13.51 KB | dynv | |
| drupal-statistics_advanced-Details02.png | 11.94 KB | dynv | |
| drupal-statistics_advanced-Details01.png | 12.15 KB | dynv | |
| drupal-statistics_advanced-Recent_hits.png | 22.54 KB | dynv |
Comments
Comment #1
dynv commentedHere's the text version of these examples : http://dynv.qc.to/content/text-version-examples-skip-node-recent-hits