Search Watchdog Log

These queries are not secure. If someone manages to extend an administrator's session information (through a bug elsewhere), they would be able to execute SQL queries.

I wouldn't fix the problem. The solution is to properly use the dababase API. That is, to use the '%s' and %d directives.

lots of it. *shudder*

this would still be a useful feature. Moving to 6.x-dev queue.

Patch has no relationship to current module.

Rather than maintain http://drupal.org/project/logsearch, perhaps I'll try rolling some small part of it into core.

I guess I can't get this involved right now.

#445482: Convert dblog_build_filter_query() to DBTNG needs to be resolved before this can happen

This is where I was headed with this feature when I discovered #445482: Convert dblog_build_filter_query() to DBTNG. :s replacement doesn't work for u.name in this method because of the open bug. As this patch is, it would only add user searching, not text message text. Since the text portion of the watchdog log string has replacement values in it between the message and variables fields, that becomes a larger issue of discussion.

I don't know the way this patch goes, neither why it is postponed
but I'm providing patches and modules to achieve this

patch providing log_filters hook for D7 #582622: provide hook for dblog_filters
same patch for D6 #582672: dblog support filters through a hook (6.x)

alternatively a set of working modules for D6 #578488: recent/aged/username/hostname filters for log entries
(with screenshots available)

everything waiting for user to test and give feedback

do you really would like to see this into D7 core?
come on! code freeze is here already!

Is the dblog / watchdog data available to views and / or rules / trigger /actions?
That would be great, as i need to do a lot of hand holding for user login and password reset. Could have better monitoring, automatic emails and reports,...

marked #444654: admin/reports/dblog should allow filtering by user as a duplicate of this

shouldn't this be marked closed (won't fix) because who doesn't want to manually search through logs when they get about 2000 log entries per day.. finding that error message from last night should be an hour long endeavor, no?

@treksler (and others): Help get #445482: Convert dblog_build_filter_query() to DBTNG in instead of being snarky.

the watchdog data is available to views
#1874534: Introduce a dblog / watchdog views integration
#2015149: Replace dblog recent log entries with a view