Change Details

Currently envoy includes a field in the access log if the value is null, but eventgate fails validation on it cause we do not allow nulls in our schemas - analytics chokes on nulls. The cleanest way is to propose removing nulls in envoy itself, but we can remove them with some lua in fluent-bit, or optionally remove them in eventgate.

- Envoy 1.16 will support nested JSON in log format https://github.com/envoyproxy/envoy/pull/12602 - this needs to be utilized, nest filters in fluent-bit config can be removed then. - Envoy 1.16 will be capable of filtering out nulls natively https://github.com/envoyproxy/envoy/issues/12735 - this needs to be utilized, fluent-bit Lua Filter can be removed then.

Currently envoy includes a field in the access log if the value - Envoy 1.16 will support nested JSON in log format https://github.com/envoyproxy/envoy/pull/12602 - this nulleeds to be utilized, but eventgate fails validation on it cause we do not allow nulls in our schemas - analytics chokes on nulls. The cleanest way is to propose removing nulls in envoy itself, but we can remove them with some lua in fluent-bitnest filters in fluent-bit config can be removed then. - Envoy 1.16 will be capable of filtering out nulls natively https://github.com/envoyproxy/envoy/issues/12735 - this needs to be utilized, or optionally remove them in eventgatefluent-bit Lua Filter can be removed then.