You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Save this file as values.yaml.
The text was updated successfully, but these errors were encountered: