luis.silva
Hey, any update on this?
yes OTEL is on kong.conf tracing_instrumentations = all tracing_sampling_rate = 0.25 and on kong.yml as a global plugin
After a deploy that disable the OTEL for all requests tracing_instrumentations = off tracing_sampling_rate = 0 
I activated the OTEL again but this time with request instrumentation only. tracing_instrumentations = request tracing_sampling_rate = 0.25 And the system beaves normally without impacts
Hi, Sorry for the low information about the issue. Yes, the main problem is memory consumption, and because of that, we saw the nginx pids being released ( gracefully ),...
Any news related to this? For instance, we need to split the EventSeverity into a dedicated field in order to not INDEX several levels like INFO, VERBOSE etc...
I'm having the same problem that @liukaiyuliukaiyu mentioned. I created a custom plugin in Kong with this library and have several timeouts connecting and doing authentication through Redis. My setup...
@liukaiyuliukaiyu did you already apply any mitigation or workaround for this issue? Im using Azure Fsv16 machines and using only 8 workers for kong, that way I guarantee a set...
You may control the breaking change, but it will add extra complexity. For instance, you can support the split by "," but you need to guarantee that the next item...
sure, but my point is why encode does not throw an error?