update AMP collector configuration #868
Conversation
ratnopamc
requested review from
aws-ia-ci,
parkand1,
shapirov103,
youngjeong46,
elamaran11 and
a team
as code owners
|
@shapirov103 Could we run e2e here? |
| resources: | ||
| limits: | ||
| cpu: "1" | ||
| memory: "2Gi" |
There was a problem hiding this comment.
Should not this be configurable? Do you foresee cases that this particular constraint won't work in production for larger volumes?
There was a problem hiding this comment.
This could be made configurable but this configuration is for collector so we dont run in to constraint in production also this is the config received from service team.
There was a problem hiding this comment.
I am not questioning the need for the settings, I actually like them. We can apply for now, but these are hard coded and there will be no way for customers to override them if needed. Let's wait for the customer signals ;)
|
/do-e2e-tests |
|
Ran e2e for aws observability accelerator Graviton and OSS Patterns with latest otel collector. works as intended |
Issue #, if available:
#863
Description of changes:
Updated AMP collector configuration to use latest otel collector image and also set request and limits.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.