Skip to main content

OTEL-026: batch timeout above 60s

Severity: warn (advisory)

Rule Details​

A batch.timeout above 60s means telemetry can sit in the Collector's in-memory queue for over a minute before it leaves. That delays alerts, inflates memory usage during traffic spikes, and multiplies data loss on crash because more data is buffered at any given moment. 60s is already generous for almost every workload.

This rule fires when batch.timeout > 60s.

Options​

FieldConstraint
timeoutShould be ≤ 60s

Examples​

Avoid
processors:
  batch:
    timeout: 120s                    # too long
Prefer
processors:
  batch:
    timeout: 5s

When Not To Use It​

Cold-archive pipelines where you deliberately want huge batches written to object storage. Even then, 60s is usually enough.

  • OTEL-025 — batch timeout below 100ms
  • OTEL-023 — batch send_batch_max_size unset

Version​

Available since augur v0.1.0.

Further Reading​

Resources​