Sema Deployment Event Logging -> Kubernetes Pod Logs: Multi‑Pod Aggregation Behavior

When a Sema‑managed deployment fails, the Deployment Event Logging feature attaches the associated Kubernetes pod logs to the deployment event record. The documentation confirms that logs are emitted to a shared stream queryable by the Sema CLI and API, but it does not specify whether Sema automatically merges logs from multiple pods into a single event entry or leaves the aggregation to the user. This uncertainty becomes relevant when troubleshooting multi‑pod failures, as the way logs are grouped affects how quickly a root cause can be identified.

Given that log retention can be extended and cluster‑wide logging policies may override Sema’s defaults, the exact behavior may vary across Sema 1.x and 2.x releases. Clarifying the aggregation model would help teams decide whether they need to implement additional correlation logic in their observability pipelines.

Does Sema consolidate logs from all pods belonging to a failed deployment into a single event stream entry? If not, what mechanism does Sema provide for users to correlate pod logs with the deployment event? Are there configuration flags that control this aggregation behavior?