DNSTAP overload condition logging

Hi, how can a BIND 9 operator detect an DNSTAP overload condition? My understanding is that BIND 9 worker threads write DNSTAP information into a circular buffer in memory, which is that read by a different thread to write out the data (to file or socket). Is there any indication to the user

Re: DNSTAP overload condition logging

Hi Carsten, From our reading of the code, it appears that when the buffer fills up, it refuses to accept new entries. Older events are not overwritten, but newer events are refused. The fstrm_iothr_submit() function can return success, failure, or “fstrm_res_again”, which indicates the queue is

Re: DNSTAP overload condition logging

Hi Chris, Chris Buxton writes: [[PGP Signed Part:Undecided]] Hi Carsten, From our reading of the code, it appears that when the buffer fills up, it refuses to accept new entries. Older events are not overwritten, but newer events are refused. The fstrm_iothr_submit() function can return su