Request for better audit log filtering

[ikkerens]

A sentiment I often see across bot developers is that they wish to be able to build better logging tools for moderative events. As a result something we've often seen is the request to add the moderator ID / reason to affects events.

For example, GUILD_MEMBER_REMOVE could potentially include the kicking moderator and reason.
MESSAGE_DELETE could include the moderator that deleted the message.
As this has been requested often I'm not going to request it again but leave it here for context.

In a recent other issue, @night referred to using the Audit Log to get this information, seen here: #756 (comment).

However, right now that requires us to scour the audit log hoping to find a matching entry which might or might not even be accurate. So as a result, would it perhaps be possible to also add a target_id query parameter when querying the audit log? Where target_id could refer to the user that was kicked, not the moderator that executed it. Or the message_id that was deleted.
Right now the endpoint does not allow us to do so as the user_id only searches for the executing member: https://discordapp.com/developers/docs/resources/audit-log#get-guild-audit-log

Naturally, we'd still prefer getting this information passed in the gateway event, but if this is not possible, making the audit log ever so slightly more useable would be amazing.

[spydacarnage]

I've recently needed to start checking the audit log for nickname changes, and I second this request for better filtering in the hope of seeing some implementation.

Being able to search by target_id would be really helpful (maybe make it so that it only works if you supply an action_type parameter, if that would make it easier?)

And also, in addition to being able to filter before a certain Id, it would be helpful to be able to search after an Id. This could seriously reduce the amount of data being transferred.