TertiumOrganum1
TertiumOrganum1
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
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...
yes, project is obsolete and unmaintained
> We'll implement a full-blown opentelemetry implementation using OTLP and gRPC collector soon. So current implementation will be deprecated. Do you mean otel http/grpc exporter in background (otlp push model)...
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/
agree > I'd suggest adding another `Process` override, which takes more data from consumer and by-default just calls `Process(std::string)`. This way we could change consumer implementation to call the newly...
@itrofimow please check: https://github.com/userver-framework/userver/pull/605
Yes, very interested in asyncapi support too! Especially ver 3.0,which is much clearer and richer than 2.x.
Hi! Received an email with this link, but can't find this Lars's post here and it looks like this repo is still private. https://github.com/LarsArtmann/typespec-asyncapi Any clarifications are welcome 😉