http://www.johnandcailin.com/blog/cailin/log4drupal-logging-api-drupal

I was discussing with Killes one of the challenges of running Drupal.org was the increasing amount of maintainers and book maintainers. He expressed concerned about the lack of granular monitoring available for 91 maintainers and 150 book maintainers.

Perhaps this log4drupal instance might help.

Comments

kbahey’s picture

kbahey commented

I don't know how this will help. Can you explain?

Also, see the comments on the blog post where people say this is already done by trace and debug modules, as well as the new watchdog hook in D6, which allows modules to customize logging.

heine’s picture

heine commented
Assigned: Unassigned » Amazon
Status: Active » Closed (won't fix)

What we need for Drupal.org is a module that can quickly answer questions such as:

Who blocked User N?
Who promoted node N to the front page?
Who demoted node N from the front page?
Who added a trademark statement to the footer?
Who added the blog about LOLCATS to Planet? (with a link to strip all permissions from this user :)

Drupal.org is not unique in this regard, and I expect some modules to surface soon.

heine’s picture

heine commented
Status: Closed (won't fix) » Active

Fixing the spontaneous (!) issue change. Sorry.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Fixed

We have deployed the role_activity module which solves the issue to some degree.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.