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.

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

scrape_interval configuration to be updated while creating ADOT add on in EKS #640

Open
vbhatt91 opened this issue Aug 28, 2023 · 3 comments

Comments

@vbhatt91
Copy link

Is your feature request related to a problem? Please describe.
I would like to modify or keep custom value for 'scrape_interval' parameter in adot collector through the configuration from the add-on.

Describe the solution you'd like.
To have this configuration editable under optional configuration settings (configuration values) while creating the ADOT add on in EKS cluster.

Describe alternatives you've considered.
Manually editing the 'opentelemetrycollector' k8s object to update the values using below command.
--> $ kubectl edit opentelemetrycollector/my-collector-amp -n opentelemetry-operator-system

@mhausenblas
Copy link
Member

Do you mean you want to express this in the advanced config?

@vbhatt91
Copy link
Author

Do you mean you want to express this in the advanced config?

Yes, if it is available via directly in advanced config then we can manage the parameter from Add on configuration itself.

@teokeecheng
Copy link

Currently the scrape interval is 15s, and it is too frequent and it cost a huge amount of money due to the usage of Amazon Managed Prometheus. Allowing us to update at least this scrape_interval allows more flexibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants