https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# support
s
This message was deleted.
p
Are you installing as docker standalone or kubernetes?
a
kubernetes
here is what my values look like
Copy code
global:
  storageClass: gp2
  cloud: aws
schemaMigrator:
  enabled: true
  name: "schema-migrator"
frontend:
  name: "frontend"
  replicaCount: 1
  service:
    annotations:
      <http://service.beta.kubernetes.io/aws-load-balancer-scheme|service.beta.kubernetes.io/aws-load-balancer-scheme>: "internet-facing"
    type: LoadBalancer
    port: 3301
clickhouse:
  installCustomStorageClass: true
  allowedNetworkIps:
    - "127.0.0.1"
    - "176.24.0.0/16"
    - "::/0"
because i was getting the migrotor error, thats when i decided to add
Copy code
schemaMigrator:
  enabled: true
  name: "schema-migrator"
p
schema migrator job depends on clickhouse to be healthy. And rest of the SigNoz components depend on migrator job to be executed
Can you share output of following?
Copy code
kubectl get pods,job -n platform
I see clickhouse cluster is healthy and no sign of migrator job/pod
can you try running the following command in one terminal while 
helm upgrade ...
in another terminal?
Copy code
kubectl get pods -n platform -w
If migrator pod never spawn, something is not right.
Also, do share version of K8s, Helm as well as signoz helm chart being used
a
using kubernetes 1.28 on eks, i am using helm resources on terraform, the latest helm version, v3.13.2, and the signoz chart version is "0.31.2"
here is the outcome of the commands
everything works now but i am getting a new erro from my otel-collector-metrics pod
p
That happens when the metrics exporter are not working for the pods with scrape annotation enabled.
Do check with curl in the pods mentioned and their port with 
/metrics
suffix if they return the metrics data
a
something like this right
Copy code
curl <http://signoz-otel-collector-metrics.platform.svc.cluster.local:13133/metrics>
6 Views
Open in Slack
PreviousNext
Powered by