Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[processor/memorylimiter] Remove deprecated ballast_size_mib config from examples #9085

Merged
merged 2 commits into from
Apr 5, 2022
Merged

[processor/memorylimiter] Remove deprecated ballast_size_mib config from examples #9085

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d470448
[processor/memorylimiter] Remove deprecated ballast_size_mib config f…
mar4uk Apr 5, 2022
2bfe78c
Merge branch 'main' into memorylimiterprocessor-fix-usage-in-examples
Apr 5, 2022
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
9 changes: 3 additions & 6 deletions exporter/sapmexporter/examples/signalfx-collector.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,15 +45,12 @@ processors:
#action: insert
# Enabling the memory_limiter is strongly recommended for every pipeline.
# Configuration is based on the amount of memory allocated to the collector.
# The configuration below assumes 2GB of memory. In general, the ballast
# should be set to 1/3 of the collector's memory, the limit should be 90% of
# The configuration below assumes 2GB of memory. In general, the limit should be 90% of
# the collector's memory up to 2GB, and the spike should be 25% of the
# collector's memory up to 2GB. In addition, the "--mem-ballast-size-mib" CLI
# flag must be set to the same value as the "ballast_size_mib". For more
# information, see
# collector's memory up to 2GB.
# For more information, see
# https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/memorylimiterprocessor/README.md
memory_limiter:
ballast_size_mib: 683
check_interval: 2s
limit_mib: 1800
spike_limit_mib: 500
Expand Down
9 changes: 3 additions & 6 deletions exporter/sapmexporter/examples/signalfx-k8s.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,15 +55,12 @@ data:
#action: insert
# Enabling the memory_limiter is strongly recommended for every pipeline.
# Configuration is based on the amount of memory allocated to the collector.
# The configuration below assumes 2GB of memory. In general, the ballast
# should be set to 1/3 of the collector's memory, the limit should be 90% of
# The configuration below assumes 2GB of memory. In general, the limit should be 90% of
# the collector's memory up to 2GB, and the spike should be 25% of the
# collector's memory up to 2GB. In addition, the "--mem-ballast-size-mib" CLI
# flag must be set to the same value as the "ballast_size_mib". For more
# information, see
# collector's memory up to 2GB.
# For more information, see
# https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/memorylimiterprocessor/README.md
memory_limiter:
ballast_size_mib: 683
check_interval: 2s
limit_mib: 1800
spike_limit_mib: 500
Expand Down