max_coalescing_delay log event

Q: Will max_coalescing_delay trigger a log event?

A: The knowledge sources indicate that the max_coalescing_delay parameter in Kong Gateway plugin queues sets the maximum number of seconds to elapse after the first entry was queued before the queue starts calling the handler (i.e., sending the batch to the upstream server). However, there is no explicit information in the provided sources stating that reaching or triggering max_coalescing_delay itself will generate a log event.

The documentation does mention that warning log entries are produced when the queue reaches 80% of its capacity or when entries are deleted due to the queue being full, but it does not mention similar logging for max_coalescing_delay events. Therefore, based on the available information, it appears that max_coalescing_delay controls batching timing but does not itself trigger a log event when the delay is reached and a batch is sent HTTP Log plugin queuing OpenTelemetry plugin queuing.

If you need confirmation about logging behavior specifically for max_coalescing_delay, you may need to consult Kong Gateway's runtime logs or reach out to Kong support, as the knowledge sources do not explicitly mention this detail.

Size: S
DoD:
Find out whether max_coalescing_delay triggers a log event in all plugins that support queues:

• OpenTelemetry
• Datadog
• StatsD
• Zipkin
• HTTP Log

You should be able to check the plugin code and see if this happens. Point Claude at the plugin source files.

There is an include used for the queueing docs between these plugins. Update the include with the relevant info.

Read the source for the OpenTelemetry, Datadog, StatsD, Zipkin, and HTTP Log plugins, focusing on queue handling when max_coalescing_delay is reached. Confirm whether that path emits a log event, then update the shared queueing documentation include with the relevant behavior for each plugin.