| /openbmc/phosphor-logging/docs/ |
| H A D | structured-logging.md | 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
[all …]
|
| /openbmc/qemu/nbd/ |
| H A D | client.c | 1441 len = sizeof(chunk->structured); in nbd_receive_reply_chunk_header()
1455 chunk->structured.flags = be16_to_cpu(chunk->structured.flags); in nbd_receive_reply_chunk_header()
1456 chunk->structured.type = be16_to_cpu(chunk->structured.type); in nbd_receive_reply_chunk_header()
1457 chunk->structured.cookie = be64_to_cpu(chunk->structured.cookie); in nbd_receive_reply_chunk_header()
1466 payload_len = be32_to_cpu(chunk->structured.length); in nbd_receive_reply_chunk_header()
1474 chunk->structured.type, in nbd_receive_reply_chunk_header()
1475 nbd_rep_lookup(chunk->structured.type)); in nbd_receive_reply_chunk_header()
1478 chunk->structured.length = payload_len; in nbd_receive_reply_chunk_header()
1575 type = nbd_reply_type_lookup(reply->structured.type); in nbd_receive_reply()
1576 trace_nbd_receive_reply_chunk_header(reply->structured.flags, in nbd_receive_reply()
[all …]
|
| H A D | trace-events | 68 nbd_co_send_chunk_done(uint64_t cookie) "Send structured reply done: cookie = %" PRIu64
69 …ead(uint64_t cookie, uint64_t offset, void *data, uint64_t size) "Send structured read data reply:…
70 nbd_co_send_chunk_read_hole(uint64_t cookie, uint64_t offset, uint64_t size) "Send structured read …
72 …(uint64_t cookie, int err, const char *errname, const char *msg) "Send structured error reply: coo…
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-objectpath_0.6.1.bb | 1 DESCRIPTION = "The agile NoSQL query language for semi-structured data"
|
| /openbmc/u-boot/fs/jffs2/ |
| H A D | Kconfig | 5 Flash File System version 2). JFFS2 is a log-structured file system
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/cyaml/ |
| H A D | cyaml_1.4.1.bb | 2 DESCRIPTION = "LibCYAML is a library for reading and writing structured YAML documents."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/libconfig/ |
| H A D | libconfig_1.7.3.bb | 2 DESCRIPTION = "Library for manipulating structured configuration files"
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Spencer-86 | 11 Beware that some of this code is subtly aware of the way operator precedence is structured in regul…
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
| H A D | xkeyboard-config_2.44.bb | 4 Window. The goal is to provide the consistent, well-structured, \
|
| /openbmc/openbmc/poky/meta/recipes-gnome/libgudev/ |
| H A D | libgudev_238.bb | 32 # version as that is how the directory is structured.
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/logfsprogs/ |
| H A D | logfsprogs_git.bb | 3 LogFS is a Linux log-structured and scalable flash file system, intended \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/poke/ |
| H A D | poke_4.2.bb | 1 SUMMARY = "GNU poke is an extensible editor for structured binary data"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/protobuf/ |
| H A D | protobuf-c_1.5.1.bb | 1 SUMMARY = "Protocol Buffers - structured data serialisation mechanism"
|
| H A D | protobuf_5.29.4.bb | 1 SUMMARY = "Protocol Buffers - structured data serialisation mechanism"
2 DESCRIPTION = "Protocol Buffers are a way of encoding structured data in an \
|
| /openbmc/qemu/include/block/ |
| H A D | nbd.h | 122 NBDStructuredReplyChunk structured; member
137 QEMU_BUILD_BUG_ON(offsetof(NBDReply, structured.cookie) !=
|
| /openbmc/qemu/block/ |
| H A D | nbd.c | 764 NBDStructuredReplyChunk *chunk = &s->reply.structured; in nbd_co_receive_offset_data_payload()
808 len = s->reply.structured.length; in nbd_co_receive_structured_payload()
892 chunk = &s->reply.structured; in nbd_co_do_receive_one_chunk()
999 #define NBD_FOREACH_REPLY_CHUNK(s, iter, cookie, structured, \ argument
1001 for (iter = (NBDReplyChunkIter) { .only_structured = structured }; \
1043 chunk = &reply->structured; in nbd_reply_chunk_iter_receive()
1100 NBDStructuredReplyChunk *chunk = &reply.structured; in nbd_co_receive_cmdread_reply()
1112 ret = nbd_parse_offset_hole_payload(s, &reply.structured, payload, in nbd_co_receive_cmdread_reply()
1153 NBDStructuredReplyChunk *chunk = &reply.structured; in nbd_co_receive_blockstatus_reply()
1173 s, &reply.structured, payload, wide, in nbd_co_receive_blockstatus_reply()
|
| /openbmc/docs/ |
| H A D | anti-patterns.md | 517 [systemd-journald provides structured logging][systemd-structured-logging],
521 https://github.com/openbmc/phosphor-logging/blob/master/docs/structured-logging.md
522 [systemd-structured-logging]:
525 The concept of structured logging allows for convenient programmable access to
533 For human ergonomics `lg2` provides the ability to interpolate structured data
540 structured log event, regardless of whether any particular key is interpolated
561 structured data associated with the log entry:
577 the structured data, as well as being interpolated into `MESSAGE` as requested.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/jq/ |
| H A D | jq_1.7.1.bb | 3 filter and map and transform structured data with the same \
|
| /openbmc/phosphor-pcie-presence/ |
| D | MAINTAINERS | |
| /openbmc/openpower-sbe-interface/ |
| H A D | MAINTAINERS | 15 Section entries are structured according to the following scheme:
|
| /openbmc/openpower-inventory-upload/ |
| H A D | MAINTAINERS | 15 Section entries are structured according to the following scheme:
|
| /openbmc/openpower-logging/ |
| D | MAINTAINERS | |
| /openbmc/google-ipmi-sys/ |
| H A D | MAINTAINERS | 15 Section entries are structured according to the following scheme:
|
| /openbmc/pyphosphor/ |
| H A D | MAINTAINERS | 15 Section entries are structured according to the following scheme:
|
| /openbmc/phosphor-mboxd/ |
| H A D | MAINTAINERS | 15 Section entries are structured according to the following scheme:
|