-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/coralogix] #34837
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
sorry for delayed response, So this should be already achievable via Otel config, docs: https://opentelemetry.io/docs/collector/configuration/#environment-variables Example:
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
exporter/coralogix
Is your feature request related to a problem? Please describe.
We are using ArgoCD (GitOps) to manage all our applications, including the OpenTelemetry Collector (otel-collector). Our use case involves sending data to the Coralogix server using the Coralogix exporter.
However, we have encountered a security concern: the Coralogix exporter currently does not support passing the private key via environment variables. Instead, it requires the key to be provided in the configuration file, which poses a security risk as we do not want to store private keys in GitHub or any version control system.
Describe the solution you'd like
We would like to request support for passing the private key to the Coralogix exporter via environment variables. This feature would enhance security practices by allowing sensitive information to be managed through environment variables instead of being hardcoded or stored in configuration files.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: