[ratelimits] Logging category

Vernon Schryver vjs at rhyolite.com
Mon May 13 13:12:16 UTC 2013

> From: Masato Minda <minmin at jprs.co.jp>

> > Responses that are slipped ro dropped are logged in "queries"
> > category at the "info" level.  That is the same category and level
> > at which the query itself and any other errors are logged.  Rate
> > limit dispositions should no more than double the noise in the
> > "queries" category.   If the "queries" category is too busy (it
> > often is), consider turning of query logging.
> We (.jp) have probrem in this feature.
> a.dns.jp and g.dns.jp (.jp's NS) are logging and archiving querylog
> always in a long time. (since 2004, of course, we need huge storage.)

The rational for logging RRL in the query log is that a dropped or
slipped response is as like an error and so should logged like
SERVFAIL, FORMERR, and other errors.

However, I see that many SERVFAIL and FORMERR errors are logged in the
query-errors category with severities of "debug 1" and "debug 3".

Should the RRL slip and drop move logging from the query category to
the query-errors category with "debug 1" or "debug 3" severity?

Is it too late to change?  Are too many RRL installations parsing
logs for RRL events?

Vernon Schryver    vjs at rhyolite.com

More information about the ratelimits mailing list