Let me rephrase this to ensure that I understood the idea correctly.

So, there should be predefined categories of errors (e.g. authentication failures) and then you could configure that all errors belonging to that category should be logged with a particular facility. From your example:

• log_facility_deny_auth=LOG_USER

Further, for each category you could also define the severity, failures of that category should be logged with. From your example:

• log_level_deny_auth=WARNING

That is, all authentication failures should be logged as warnings, using the facility LOG_USER.

Actually, it seems to me that what we are talking about here is not errors (from Maxscale's perspective) but events in which the DBA or end-user might be interested.

For instance, if Maxscale denies access, then Maxscale (is most likely) not malfunctioning, but acting the way it's been configured to act. However, the fact that it denies access may be (and likely is) of interest to he DBA.

So, we need to define a set of events - e.g. access denied - of interest to a DBA and then make it a configuration issue whether they are logged at all and if they are, using what facility and severity.

This is a good idea and should be implemented. Moving to 1.4.

Removing fix version as this will not be in 1.4.