From: Otto Date: Wed, 15 Sep 2021 11:29:06 +0000 (+0200) Subject: Update docs now that a few things have changed. X-Git-Tag: dnsdist-1.7.0-alpha2~9^2~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b6ff54acf9f6bf4e9fad263b1214c9d3fa71cd4d;p=thirdparty%2Fpdns.git Update docs now that a few things have changed. --- diff --git a/pdns/recursordist/docs/performance.rst b/pdns/recursordist/docs/performance.rst index 1040b711b9..d4b59f944d 100644 --- a/pdns/recursordist/docs/performance.rst +++ b/pdns/recursordist/docs/performance.rst @@ -209,11 +209,11 @@ Currently, an event protobuf message has the following definition: .. code-block:: protobuf enum EventType { + CustomEvent = 0; RecRecv = 1; - DistPipe = 2; - PCacheCheck = 3; - SyncRes = 4; - AnswerSent = 5; + PCacheCheck = 2; + SyncRes = 3; + AnswerSent = 4; LuaGetTag = 100; LuaGetTagFFI = 101; LuaIPFilter = 102; @@ -235,12 +235,13 @@ Currently, an event protobuf message has the following definition: optional int64 intVal = 5; optional string stringVal = 6; optional bytes bytesVal = 7; + optional string custom = 8; } repeated Event trace = 23; Event traces can be enabled by either setting :ref:`setting-event-trace-enabled` or by using the :doc:`rec_control ` subcommand ``set-event-trace-enabled``. -An example of a trace (timestamps are relative in nanoseconds): +An example of a trace (timestamps are relative in nanoseconds) as shown in the logfile: .. code-block:: C