> On Oct 11, 2019, at 9:59 AM, Remi Gacogne wrote:
>
> This seems to be a limitation of dnstap-read, we do export the
> nanoseconds as defined in the dnstap format, and it looks like
> dnstap-ldns [1] read them just fine:
Oh, that is great news. Thank you! I knew the issue was somewhere in
> On Oct 11, 2019, at 11:10 AM, Casey Deccio wrote:
>
>> On Oct 11, 2019, at 9:59 AM, Remi Gacogne wrote:
>>
>> This seems to be a limitation of dnstap-read, we do export the
>> nanoseconds as defined in the dnstap format, and it looks like
>> dnstap-ldns [1] read them just fine:
>
> Oh,
Hi all,
I am using the following to log queries:
logger = newFrameStreamTcpLogger("127.0.0.1:4343")
addAction(AllRule(), DnstapLogAction("foo", logger))
Then I use this command line to read and produce yaml output:
fstrm_capture -t protobuf:dnstap.Dnstap -a 127.0.0.1 -p 4343 -w - | dnstap-read
Hi Casey,
On 10/11/19 5:31 PM, Casey Deccio wrote:
> I am using the following to log queries:
>
> logger = newFrameStreamTcpLogger("127.0.0.1:4343")
> addAction(AllRule(), DnstapLogAction("foo", logger))
>
> Then I use this command line to read and produce yaml output:
>
> fstrm_capture -t
