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

Need better explanation #282

Open
adampikulik opened this issue Aug 29, 2023 · 0 comments
Open

Need better explanation #282

adampikulik opened this issue Aug 29, 2023 · 0 comments

Comments

@adampikulik
Copy link

There is no explanation which fields are mandatory in values.yaml and how they should be set.
For example: https://github.com/coralogix/telemetry-shippers/blob/master/otel-agent/k8s-helm-windows/README.md

There should be added (from https://coralogix.com/docs/opentelemetry-using-kubernetes/):
In order to send your data to Coralogix, you are required to declare the endpoint variable into your file. Choose the OpenTelemetry endpoint for the domain associated with your Coralogix account. You have the option of sending logs, metrics, and / or traces to Coralogix. The example override file below includes all three.
You are also required to specify the mode.

For high data traffic clusters and/or to leverage Coralogix APM capabilities, we recommend daemonset mode acting as an agent running on each node. Be aware that it consumes resources (e.g., CPU & memory) from each node on which it runs.
For development environments or clusters with minimal data, we recommend deployment mode.

#values.yaml
---
global:
  domain: "<cx_domain>"
opentelemetry-collector:
  mode: "<daemonset/deployment>"

Save this file as values.yaml.

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

1 participant