https://signoz.io logo
Join Slack
Powered by
Or do I need to override the helm-values also when...
# general
b
Or do I need to override the helm-values also when upgrading?
p
@Prashant Shahi may have more ideas on this? have you checked the latest helm release? - https://github.com/SigNoz/charts
b
yes, the chart is added and udpated
I also see v0.11 in the frontend now
a
Or do I need to override the helm-values also when upgrading?
I think so.... do you see an error in applying chart? like 
replica
count not found?
b
no, everything runs successfully
Copy code
NAMESPACE: default
STATUS: deployed
REVISION: 2
NOTES:
1. You have just deployed SigNoz cluster:

- frontend version: '0.11.0'
- query-service version: '0.11.0'
- alertmanager version: '0.23.0-0.2'
- otel-collector version: '0.55.0'
- otel-collector-metrics version: '0.55.0'

2. Get the application URL by running these commands:

  export POD_NAME=$(kubectl get pods --namespace default -l "<http://app.kubernetes.io/name=signoz,app.kubernetes.io/instance=signoz-telemetry,app.kubernetes.io/component=frontend|app.kubernetes.io/name=signoz,app.kubernetes.io/instance=signoz-telemetry,app.kubernetes.io/component=frontend>" -o jsonpath="{.items[0].metadata.name}")
  echo "Visit <http://127.0.0.1:3301> to use your application"
  kubectl --namespace default port-forward $POD_NAME 3301:3301


If you have any ideas, questions, or any feedback, please share on our Github Discussions:
  <https://github.com/SigNoz/signoz/discussions/713>
a
can you show the logs of 
query-service
and 
otel-collector
?
b
yes
Copy code
time="2022-08-31T12:23:18Z" level=error msg="dial tcp: lookup signoz-telemetry-clickhouse on 172.20.0.10:53: no such host" component=clickhouse
time="2022-08-31T12:23:18Z" level=error msg="dial tcp: lookup signoz-telemetry-clickhouse on 172.20.0.10:53: no such host" component=clickhouse
time="2022-08-31T12:23:23Z" level=error msg="dial tcp: lookup signoz-telemetry-clickhouse on 172.20.0.10:53: no such host" component=clickhouse
time="2022-08-31T12:23:23Z" level=error msg="dial tcp: lookup signoz-telemetry-clickhouse on 172.20.0.10:53: no such host" component=clickhouse
hmm
seems that the clickhouse db can not be found
or service
Collector:
Copy code
error   exporterhelper/queued_retry_inmemory.go:107     Exporting failed. No more retries left. Dropping data.  {"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "max elapsed time expired dial tcp: lookup signoz-telemetry-clickhouse on 172.20.0.10:53: no such host", "dropped_items": 10}
seems to be a clickhouse problem
p
@Benedikt can you share output of the following?
Copy code
kubectl -n platform get pods -o=wide
b
Copy code
chi-signoz-telemetry-clickhouse-cluster-0-0-0              1/1     Running    0          75m     10.0.116.8     ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-alertmanager-0                            1/1     Running    0          75m     10.0.96.110    ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-clickhouse-operator-f6487b5b7-dp62l       2/2     Running    0          75m     10.0.56.105    ip-10-0-9-66.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-frontend-f8854f987-lzk8l                  1/1     Running    0          75m     10.0.4.204     ip-10-0-9-66.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-otel-collector-metrics-7d68bb49d7-kq5v7   1/1     Running    0          75m     10.0.116.25    ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-otel-collector-qfp68                      1/1     Running    0          75m     10.0.8.201     ip-10-0-9-66.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-otel-collector-qrkqt                      0/1     Init:0/1   0          75m     10.0.117.170   ip-10-0-123-32.eu-central-1.compute.internal   <none>           <none>
signoz-telemetry-otel-collector-vf2ls                      0/1     Init:0/1   0          75m     10.0.78.129    ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-query-service-0                           1/1     Running    0          75m     10.0.70.87     ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
signoz-telemetry-zookeeper-0                               1/1     Running    0          33d     10.0.85.169    ip-10-0-85-7.eu-central-1.compute.internal     <none>           <none>
it is currently installed in the default namespace
I will try to reinstall
it is in our staging system. so should be no problem
that solved the problem
Open in Slack
PreviousNext
Powered by