Page MenuHomePhabricator

Log filter hits and filter changes to Special:Log
Closed, DuplicatePublic

Description

Author: mike.lifeguard+bugs

Description:
I seem to recall a request to send filter changes to RC, but I can't find it. They should go to IRC too.

As well, please send hits (anything that goes to AbuseLog) to IRC so we can create real-time monitoring tools.


Version: unspecified
Severity: normal

Details

Reference
bz18080

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:32 PM
bzimport added a project: AbuseFilter.
bzimport set Reference to bz18080.
bzimport added a subscriber: Unknown Object (MLST).

I think I already replied to this bug (or a related one).

Please tell me what info you need for each event, and what sort of format you suggest providing it in. I have a half-done patch in my working copy.

mike.lifeguard+bugs wrote:

(In reply to comment #1)

I think I already replied to this bug (or a related one).

Please tell me what info you need for each event, and what sort of format you
suggest providing it in. I have a half-done patch in my working copy.

I doubt it'll make much difference to us what the format is. I'll CC Pathoschild since he's done lots of work on parsing RC feeds for CVNBot. The info we want is probably:

*New filters: Who created it, what actions it can take, the filter name & number, (I'd add the summary, but the notes field is too big to include, ugh)
*Editing filters: Who edited it, what actions they added/removed, the filter name & number
*Filter hits: Who hit it, the filter name & number, page name/log type for the action, what actions AF took -- so, if AF disallowed the edit, we want to see that it was an edit and that AF disallowed it. If the filter has a throttle, some indication of the throttle being incremented.

I'm not sure how AF's actions are logged right now - a pseudo-user? If so, actions like blocking or desysoping should go to normal RC (and here too). Actions that can't go to RC like removing autoconfirmed status should come here.

It will probably be useful to take a look at what info is being made available in #wikipedia-en-abuse-log (via screenscraping, ugh) since that's basically the information we want, AFAIK.

mike.lifeguard+bugs wrote:

If 'tag' is one of the options, that tag should be included in the filter hit message.

matthew.britton wrote:

#wikipedia-en-abuse-log@Freenode doesn't show everything in the log, there seems to be a list of filters that don't show (it's presumably intended for humans to read) and is thus suboptimal for machine reading. Putting the filter log in with the other stuff in the Wikimedia IRC channels would be much more useful for that (and have the usual benefits of IRC feed versus spamming API requests).

(Batch change)

These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.

Rephrasing bug to what it should be. I don't think it makes sense for AbuseFilter to explicitly send any such stuff to IRC directly. It should go through logging, which will automatically send it to irc as well.

If they are logged to Special:Log, irc goes automatically. There's no way around it.

Marking dupe of bug 19494.

  • This bug has been marked as a duplicate of bug 19494 ***