Alex Samorukov

@jakubdyszkiewicz i see that if oltp logs are specified `kuma` just configures envoy to send the logs in openmetrics format. But i did not found any retry logic/settings/documentation in envoy...

@jakubdyszkiewicz I was able to get OTLP logs working, however, it also has own problems: 1. It is not documented that openmetric logs are using GRPC, was able to find...

Actually https://github.com/kumahq/kuma/blob/master/pkg/plugins/policies/meshaccesslog/plugin/xds/configurer.go#L313 missing interpolations

@michaelbeaumont sure. ```yaml openTelemetry: body: '{"test":"value"}' ``` would render as escaped ``` "{\"test\": \"value\"}" ``` ```yaml openTelemetry: body: test: "value" ``` gets ignored and default is in use (why?) ```...

Also, i did an experiment - i tried to kill Datadog daemonset to see how errors are handled. From what i see - envoy silently dropped all messages when datadog...

From what i see in Envoy rendered config - MeshAccessLogs does not configure any retry settings ```json { "log_name": ..., "grpc_service": {...}, "transport_api_version": ..., "buffer_flush_interval": {...}, "buffer_size_bytes": {...}, "filter_state_objects_to_log": [],...

@jakubdyszkiewicz thank you. May i kindly ask to add interpolation to headers as well? As in fact, we don't need a body at all, these all could be injected as...

@jakubdyszkiewicz JFYI - example ```yaml default: backends: - type: OpenTelemetry openTelemetry: endpoint: otel-collector.observability.svc:4317 body: kvlistValue: values: - key: "mesh" value: stringValue: "%KUMA_MESH%" ``` works as expected and DataDog is happy...

JFYI, i started some pre-work at https://github.com/samm-git/amsreader-firmware/tree/zpa and will do a PR once its ready.

I like @RLovelett idea and i think i will import it. There is no any documentation of the format of the packets, so everything possible. Another suggestion is to try...