Documentation Grafana Cloud Instrument and send data Grafana Alloy Reference Components otelcol otelcol.processor.memory_limiter

otelcol.processor.memory_limiter

otelcol.processor.memory_limiter is used to prevent out of memory situations on a telemetry pipeline by performing periodic checks of memory usage. If usage exceeds the defined limits, data is dropped and garbage collections are triggered to reduce it.

The memory_limiter component uses both soft and hard limits, where the hard limit is always equal or larger than the soft limit. When memory usage goes above the soft limit, the processor component drops data and returns errors to the preceding components in the pipeline. When usage exceeds the hard limit, the processor forces a garbage collection to try and free memory. When usage is below the soft limit, no data is dropped and no forced garbage collection is performed.

You can specify multiple otelcol.processor.memory_limiter components by giving them different labels.

Usage

alloy Copy

otelcol.processor.memory_limiter "<LABEL>" {
  check_interval = "1s"

  limit = "50MiB" // alternatively, set `limit_percentage` and `spike_limit_percentage`

  output {
    metrics = [...]
    logs    = [...]
    traces  = [...]
  }
}

Arguments

You can use the following arguments with otelcol.processor.memory_limiter:

The arguments must define either limit or the limit_percentage, spike_limit_percentage pair, but not both.

The configuration options limit and limit_percentage define the hard limits. The soft limits are then calculated as the hard limit minus the spike_limit or spike_limit_percentage values respectively. The recommended value for spike limits is about 20% of the corresponding hard limit.

The recommended check_interval value is 1 second. If the traffic through the component is spiky in nature, it’s recommended to either decrease the interval or increase the spike limit to avoid going over the hard limit.

The limit and spike_limit values must be larger than 1 MiB.

Blocks

You can use the following blocks with otelcol.processor.memory_limiter:

output

Required

debug_metrics

Exported fields

The following fields are exported and can be referenced by other components:

input accepts otelcol.Consumer data for any telemetry signal (metrics, logs, or traces).

Component health

otelcol.processor.memory_limiter is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.processor.memory_limiter doesn’t expose any component-specific debug information.

Compatible components

otelcol.processor.memory_limiter can accept arguments from the following components:

• Components that export OpenTelemetry otelcol.Consumer

otelcol.processor.memory_limiter has exports that can be consumed by the following components:

• Components that consume OpenTelemetry otelcol.Consumer