lg2: update structured-logging with latest conversions

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I299eb37a617f8ba9cbeb94b63f817338a7e9a921

Address markdownlint warnings

Addressed markdownlint warnings reported by
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Tested: Verified and fixed warnings using
"../openb

Address markdownlint warnings

Addressed markdownlint warnings reported by
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Tested: Verified and fixed warnings using
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Change-Id: I6f8fe65373c748b907b9ca55c527800583983538
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: I6e8d56540a30898369d7f232d900fd74de2e7bd1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Enable lg2 log output to stderr in OpenBMC CI test

Similar to printing logs to stderr in a TTY, output to stderr can be
enabled during OpenBMC CI test by setting the `LG2_FORCE_STDERR`
environment v

Enable lg2 log output to stderr in OpenBMC CI test

Similar to printing logs to stderr in a TTY, output to stderr can be
enabled during OpenBMC CI test by setting the `LG2_FORCE_STDERR`
environment variable to any value.

Using meson, this can be done with something like:

test('test_name', executable(...), env: ['LG2_FORCE_STDERR=yes'])

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I0323fbb75fe211148ec4dc7e263fe18aabb8ffc6

show more ...

lg2: reduce stdout and allow customization

It was reported by users that the information logged to the TTY was too
much in many cases, which limited the usability of lg2. Allow users to
customize t

lg2: reduce stdout and allow customization

It was reported by users that the information logged to the TTY was too
much in many cases, which limited the usability of lg2. Allow users to
customize the output by setting the "LG2_FORMAT" environment variable
and limit the default output to just "<level> message".

Tested:

Added a simple log to the beginning of an existing daemon and tested
format strings:

```
$ ./health-monitor
<6> Here I am!
$ LG2_FORMAT="{%l} %m %% [%f:%L:%F]|%" ./health-monitor
{6} Here I am! % [int main():511:../healthMonitor.cpp]|%
```

Resolves openbmc/phosphor-logging#26.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie50c90f073539812c0693d05fc04ce7ad2b3fbcd

show more ...

lg2: support exception conversion

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4b3cb55c9d03ed04b1f072bf3f5ef98ccffb0eef

lg2: support sdbusplus enum conversion

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I78cb28697631499adf5be64f7157a894c8d887ee

lg2: introduce motivation and API

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I519756bbbf84ce024b1a117013868c3c11ebdecb