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

Values(otelcol.otlpExporter.endpoint): Does not have any effect on the template, #48

Open
Khalid-Nowaf opened this issue Jan 25, 2025 · 0 comments · May be fixed by #49
Open

Values(otelcol.otlpExporter.endpoint): Does not have any effect on the template, #48

Khalid-Nowaf opened this issue Jan 25, 2025 · 0 comments · May be fixed by #49

Comments

@Khalid-Nowaf
Copy link

I have changed the default values as the following:

otelcol:
  enabled: false 

  otlpExporter:
    endpoint: http://uptrace:14317 # <---- HERE instead of http://my-uptrace:14317
    tls: { insecure: true }
    headers: { 'uptrace-dsn': 'http://project1_secret_token@localhost:14317/1' } 

So as expect the collector to export to uptrace:14317, but the collector actually trying to connect to my-trace:14317

... error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp: lookup my-uptrace on 10.43.0.10:53: no such host\"", "dropped_items": 1387} ..

and I can see the template in the following file charts/uptrace/templates/otelcol-config.yaml has the config map as

{{ if .Values.otelcol.enabled }}
apiVersion: v1
kind: ConfigMap
metadata:
  name: otelcontribcol
  labels:
    app: otelcontribcol
    {{- include "uptrace.labels" . | nindent 4 }}
data:
  config.yaml: |
    receivers:
 ...
    exporters:
      debug:
      otlp/local:
        endpoint: http://my-uptrace:14317
        tls: { insecure: true }
        headers: { 'uptrace-dsn': 'http://project1_secret_token@localhost:14317/1' }
    service:
     ...
{{ end }}
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

Successfully merging a pull request may close this issue.

1 participant