feat: log agent exporter batcher

[jeffreylimnardy]

Description

Changes proposed in this pull request (what was done and why):

• Enable exporter helper batching in log agent using bytes sizer and values determined in the PoC.

Changes refer to particular issues, PRs or documents:

• Enable exporterbatcher in Log Agent #3506

Traceability

• The PR is linked to a GitHub issue.
• The follow-up issues (if any) are linked in the Related Issues section.
• If the change is user-facing, the documentation has been adjusted.
• If a CRD is changed, the corresponding Busola ConfigMap has been adjusted.
• The feature is unit-tested.
• The feature is e2e-tested.

[hyperspace-insights]

Control Panel

Hi, I'm an AI-powered Review Bot that helps you with summarizing and reviewing pull requests.
To interact with me, just use the following actions:

• 📝 Summarize PR
• 🔍 Review
• 🗑️ Delete all bot comments and reviews

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

What Changed

Enables the OTel Collector exporter batcher (exporterhelper batching) in the log agent by configuring a bytes-based sending queue with explicit batch size and flush timeout constraints. The change also refactors the OTLPExporterConfigBuilder to accept a SendingQueue struct directly instead of a raw integer queue size, and adds factory helpers for constructing sending queue configurations.

Affected Signal Types

Logs

Key Changes

• internal/otelcollector/config/common/types.go: Adds Sizer, Batch, SendingQueueOption types and NewSendingQueue/DisabledSendingQueue factory functions to support bytes-based exporter batcher configuration with functional options.
• internal/otelcollector/config/common/otlpexporter_config_builder.go: Replaces the raw queueSize int parameter with a SendingQueue struct throughout the builder, removing the internal queue-construction logic.
• internal/otelcollector/config/logagent/config_builder.go: Configures the log agent OTLP exporter with a bytes-sizer sending queue (200 MB max), a 2 MB minimum batch size, a 4 MB maximum batch size, and a 10-second flush timeout.
• internal/otelcollector/config/metricagent/config_builder.go, internal/otelcollector/config/otlpgateway/config_builder_logs.go, internal/otelcollector/config/otlpgateway/config_builder_metrics.go, internal/otelcollector/config/otlpgateway/config_builder_traces.go: Updated call sites to use common.NewSendingQueue(queueSize) in place of the raw integer.

Notes for Reviewers

The bytes-based batcher constants (200 MB queue, 2–4 MB batch, 10 s flush) come from ADR-029 and the associated PoC. The issue notes that the exporter batcher may expose new metrics; those need to be reviewed for integration into self-monitor alerts and OPS dashboards before this is considered fully complete. E2E tests are not yet in place.

Release Notes Input

Recommended Action: Review whether the new exporter batcher metrics (exposed by the OTel Collector exporterhelper batching feature) need to be incorporated into your self-monitor alerts or OPS dashboards.

Logs: The log agent OTLP exporter now uses the exporterhelper exporter batcher with a bytes sizer. Batches are flushed when they reach 2–4 MB or after 10 seconds, replacing implicit batching from the filelog receiver's BatchingLogEmitter. The sending queue is capped at 200 MB.

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.20.51

• GithubContextProvider: Enable exporterbatcher in Log Agent #3506
• Event Trigger: issue_comment.edited
• Summary Prompt: PR Prompt File
• Correlation ID: cbc4c0c6-1777-408e-b2b8-d6d8de64b6d1
• Output Template: PR Template File
• File Content Strategy: Full file content
• LLM: anthropic--claude-4.6-sonnet

[hyperspace-insights]

The PR is well-structured overall — the refactoring from a raw queueSize int to a SendingQueue value type with functional options is a clean improvement, and the log agent batching configuration follows the PoC findings. Two issues were flagged: a typo in a comment, and a potential time.Duration YAML serialization bug where the FlushTimeout field may marshal as nanoseconds instead of the "10s" string the golden file and OTel Collector expect — this should be verified and likely changed to string to match the pattern used by RetryOnFailure.

PR Bot Information

Version: 1.20.51

• Agent Instructions:
  • CLAUDE.md
• Correlation ID: a0e9acbc-c04c-4b1e-acdb-18377f85e7ce
• File Content Strategy: Full file content
• Event Trigger: issue_comment.edited
• LLM: anthropic--claude-4.6-sonnet
• Review Focus Files:
  • https://github.com/kyma-project/telemetry-manager/blob/d5cc75e9faf4405b05b8f42bec304ca79879fae8/.hyperspace/pull_request_bot_review_focus.md