Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSON logging format #180

Open
apolukhin opened this issue Oct 31, 2022 · 3 comments
Open

JSON logging format #180

apolukhin opened this issue Oct 31, 2022 · 3 comments
Labels
big A big feature

Comments

@apolukhin
Copy link
Member

At the moment 'tskv' and 'ltsv' logging formats are supported

enum class Format { kTskv, kLtsv, kRaw };

JSON format is a popualr logging format, it should be supported too.

@apolukhin apolukhin added help wanted We would appreciate PR big A big feature labels Oct 31, 2022
@TertiumOrganum1
Copy link
Contributor

voting for json, but also it would be nice to have a simple format for local output, ideally - to select fields for output. for example, timestamp and msg only

@TertiumOrganum1
Copy link
Contributor

TertiumOrganum1 commented Apr 25, 2024

It would be nice to have out if the box 'otlp json' format option for logger 'opentracing' (should be also renamed to 'opentelemetry' or 'otel', as opentracing standard is archived since 2022). Protobuf schema described here: https://github.com/open-telemetry/opentelemetry-proto/blob/v1.3.0/opentelemetry/proto/trace/v1/trace.proto
Json mapping looks like: https://www.honeycomb.io/blog/test-span-opentelemetry-collector

@apolukhin apolukhin removed the help wanted We would appreciate PR label Apr 26, 2024
@apolukhin
Copy link
Member Author

Thanks to all the contributors, we now have an understanding of how such logging should look like. Will adopt the functionality and features soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big A big feature
Projects
None yet
Development

No branches or pull requests

2 participants