Runtime audit configuration is currently implemented as 2 commands - setAuditConfig and getAuditConfig - that allow for setting and retrieving audit filters cluster-wide. Now that setClusterParameter and getClusterParameter provide a generalized way of doing this for any cluster server parameter, audit filters can be re-implemented as cluster server parameters that are retrieved and set via these commands instead.

For the sake of backwards compatibility, setAuditConfig and getAuditConfig will continue to work from a client's perspective and will effectively turn into aliases for the corresponding invocations of setClusterParameter and getClusterParameter.