Last modified: 2014-03-16 17:09:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14601 - Use wfDebugLog instead of wfDebug by default
Use wfDebugLog instead of wfDebug by default
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-06-20 16:06 UTC by Christian Neubauer
Modified: 2014-03-16 17:09 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Christian Neubauer 2008-06-20 16:06:52 UTC
It is currently difficult to see only a specific type of debug information, for example, only SQL queries to the database.  The user has to filter through the main debug log deleting all the stuff they aren't interested in.

It would be useful if users could define $wgDebugLogGroups to see specific types of debugging.  I propose having all classes use wfDebugLog instead of wfDebug.  For example the various database access classes could do wfDebugLog( 'database', $msg ) instead of wfDebug( $msg ).  Then if a user wanted to see all database interaction, they could just define a $wgDebugLogGroups for 'database'.

Since wfDebugLog by default just passes messages to wfDebug if no log is defined in $wgDebugLogGroups, the default logging behavior would be exactly the same as it is now.

Aside from database interaction, caching, and authentication could be logged to different logs.
Comment 1 Nigel Jones 2008-07-07 09:23:32 UTC
I've started this locally, I'd say something like 'database' 'article' 'user' 'upload' (also import) and 'other' as defaults, however there are times when it all overlaps, so I'm not sure how productive that would be.  That said, I'll give it a shot.
Comment 2 Quim Gil 2013-03-09 19:34:52 UTC
Is this request still relevant? And shouldn't be filed under Logs component?
Comment 3 Christian Neubauer 2013-03-11 11:20:52 UTC
It's still relevant in that the core code still uses wfDebug instead of wfDebugLog in most places. I really don't care one way or the other any more though so in that sense it's no longer relevant. Feel free to close or whatever...
Comment 4 Antoine "hashar" Musso (WMF) 2013-03-11 17:12:43 UTC
Yes this bug is still relevant :-]  Having almost everything logged by wfDebug() is not very helpful.
Comment 5 Krinkle 2013-05-02 01:36:49 UTC
(In reply to comment #2)
> Is this request still relevant? And shouldn't be filed under Logs component?

Logs component is about wiki user log events (Special:Log, 'logging' database etc.).

This bug is about debug logs generated by the software for developers.
Comment 6 Bryan Davis 2013-12-04 16:33:15 UTC
Related RFC at [[:mw:Requests_for_comment/Structured_logging]]
Comment 7 Daniel Norton 2014-03-16 17:09:57 UTC
Related: Bug 62713 - wfDebugLog timestamp should show fraction of second
(includes patch)

Note You need to log in before you can comment on or make changes to this bug.