Lines Matching refs:structured

3 There are currently two APIs for structured logging:
8 ## Why structured logging?
15 structured logging. As a result, there are some designs in place where specific
16 structured events are added to the journal and downstream these events can be
18 journal structured data to stored and later retrieve SEL events.
21 form of IPC, the value of structured logging persists. It is very common as part
26 structured logging the format is somewhat static and easily parsed.
28 A specific example of where structured logging is beneficial is a service which
32 expression (likely). With structured log, specific identifiers can be used as
229 trying to create structured logging. `{fmt}` doesn't address that problem
248 (2) Adding robust formatting would lead to less consistent structured data with
265 Utilizing `{fmt}` for each structured data element would impose much greater
267 string objects for N structured data elements), or we do them in the library
287 > Doesn't duplicating the structured data in the message decrease the available
291 binary format. Since the data embedded in the message and the structured data
293 compress exceptionally well. Likely on the order of 1-2 bytes per structured
298 Unless we dispense with structured logging entirely, this duplication seems like
311 would require structured data elements be in specific order and could be error