mirror of
https://github.com/hanzoai/telemetry.git
synced 2026-10-30 20:01:49 +00:00
2623e13563
**Description:** Following https://github.com/open-telemetry/opentelemetry-collector/issues/8632, this change introduces memory limiter as an extension. This allows us to place the component to reject incoming connections due to limited memory, providing better protection from running out of memory. missing feature: receiver fairness. issue where a receiver hogs all the resource can happen. **Link to tracking Issue:** <Issue number if applicable> https://github.com/open-telemetry/opentelemetry-collector/issues/8632 --------- Co-authored-by: Dmitry Anoshin <[email protected]>
19 lines
825 B
YAML
19 lines
825 B
YAML
# check_interval is the time between measurements of memory usage for the
|
|
# purposes of avoiding going over the limits. Defaults to zero, so no
|
|
# checks will be performed. Values below 1 second are not recommended since
|
|
# it can result in unnecessary CPU consumption.
|
|
check_interval: 5s
|
|
|
|
# Maximum amount of memory, in MiB, targeted to be allocated by the process heap.
|
|
# Note that typically the total memory usage of process will be about 50MiB higher
|
|
# than this value.
|
|
limit_mib: 4000
|
|
|
|
# The maximum, in MiB, spike expected between the measurements of memory usage.
|
|
spike_limit_mib: 500
|
|
|
|
# the maximum amount of memory, in %, targeted to be allocated by the process
|
|
limit_percentage: 0
|
|
|
|
# the maximum, in percents against the total memory, spike expected between the measurements of memory usage.
|
|
spike_limit_percentage: 0 |