luis.silva
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...