Lines Matching full:logs

39 to stream logs. Optionally, create a ``FilterMap`` with ``Filter`` objects with
58 Sample RPC logs request
60 The log listener, e.g. a computer, requests logs via RPC. The log service
73 Logs are streamed via RPC to a computer, and to another log listener. There can
129 out if logs were dropped during transmission.
135 using a different protocol for logs and RPCs over the same interface(s).
138 to retrieve and modify filters. The client may also stop streaming the logs by
140 interface. Note that ``Cancel()`` may lead to dropped logs. To prevent dropped
141 logs use ``RequestCompletion()`` and enable :c:macro:`PW_RPC_COMPLETION_REQUEST_CALLBACK`
148 An ``RpcLogDrain`` reads from the ``MultiSink`` instance that buffers logs, then
160 logs without the need to request them. This is useful in cases where the
162 when reconnected without the client requesting logs again if the error handling
179 count with the logs if desired.
198 rate limit logs by introducing a limit to how many logs can be flushed from
200 handle the flushed logs. For example, if the rate limiting is configured to 2
206 Rate limiting is helpful in cases where transient bursts of high volumes of logs
213 Rate limiting log drains is particularly helpful for systems that collect logs
215 early boot logs until the logging thread starts). If a very full log buffer is
226 stream that is started without the need to receive an RCP request for logs.
234 Unfortunately, logs can be dropped and not reach the destination. This module
236 possible. Logs can be dropped when
238 - They don't pass a filter. This is the expected behavior, so filtered logs will
239   not be tracked as dropped logs.
241   undrained entries; when new logs come in, old entries are dropped. The log
242   stream will contain a ``LogEntry`` message with the number of dropped logs.
245       Dropped 15 logs due to slow reader
249   ``LogEntry`` message with the number of dropped logs.
252       Dropped 15 logs due to slow reader
269   contain a ``LogEntry`` with an error message and the number of dropped logs
274       Dropped 10 logs due to writer error
277   interface interruption. Clients can calculate the number of logs lost in
281       Dropped 50 logs due to transmission error
379 Example of a log backend implementation, where logs enter the ``MultiSink`` and
406    // Tokenized logs are typically 12-24 bytes.