Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions gdi/opentelemetry/components/memory-limiter-processor.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,13 +36,10 @@ To activate the resource processor, add ``memory_limiter`` to the ``processors``

Define the ``memory_limiter`` as the first processor in the pipeline, immediately after the receivers, to ensure that backpressure can be sent to applicable receivers, and to minimize the likelihood of dropped data when ``memory_limiter`` gets triggered.

Along with the ``memory_limiter`` processor, it's highly recommended to configure the Ballast extension as well on every Collector. The ballast should be configured to be 1/3 to 1/2 of the memory allocated to the Collector.

See the following example:

.. code-block:: yaml


processors:
memory_limiter:
check_interval: 1s
Expand All @@ -53,7 +50,6 @@ To complete the configuration, include the processor in any pipeline of the ``se

.. code-block:: yaml


service:
pipelines:
metrics:
Expand Down
Loading