Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Is this possible? Would make for much more accurate data on sites with page cache enabled for anonymous users.
Comments
Comment #1
malc0mn CreditAttribution: malc0mn commentedThat would indeed be a good idea. Would have to check if it is possible. All data is logged in a shutdown function and I'm not sure if the user object is still accessible at that point of the script execution. If it is, then it is definitely possible and would be a great addition!
Comment #2
mstrelan CreditAttribution: mstrelan commentedNot at a computer at the moment, but I know devel module checks a global in its register shutdown function so i guess if Drupal is unsetting the uid you should be able to record your own uid variable earlier and have it available at shutdown.
Comment #3
mstrelan CreditAttribution: mstrelan commentedAlso
performance_shutdown()
already callsperformance_log_details()
which checks the uid, so this is definitely possible.Comment #4
malc0mn CreditAttribution: malc0mn commentedI'm a bit confused now, as I was working on Drush integration yesterday... It already shows anonymous vs logged in users in the detail page. This data has always been recorded (phew ;-) )
You do propose something like this:
right?
Comment #5
mstrelan CreditAttribution: mstrelan commentedYep, not interested in the detail page, just the summary reports as per the issue title ;)
Comment #6
malc0mn CreditAttribution: malc0mn commentedTODO: Whether the user is anonymous or not is always recorded but is simply not stored with the summary data. The table needs to be expanded with an 'anon' field so that the primary key will become path + anon.
For memcache, apc and zend we would have to generate different keys. Now based on path, afterwards based on path + anon. This will double the memory used!
If it'll be built, there has to be a setting for this: 'separate anonymous users in summary logging' with a warning that it will consume twice the amount of storage.
Maybe even better for summary logging, a list of options: