This message was deleted.

Hey team. We're in the process of evaluating SigNoz. I was attempting to get it spun up on a Talos K8 cluster, but am not getting any kubernetes/pods metrics. Just installing a fresh

signoz/signoz

at

0.50.0

helm chart with default values sets everything up properly, no errors, but I am not getting any Kubernetes metrics out of the box. I read the documentation at https://signoz.io/docs/install/kubernetes/others/ and it stated the k8s-infra chart should be included, but as of https://github.com/SigNoz/charts/commit/a99b93fbc32801eca528e9046eddcc68a625d5ae, it appeared to be removed as a dependency. I deployed the

k8s-infra

helm chart with default values and still no cigar. I don't see any errors on any of these pods logs, storage is provisioned correctly. It appears

k8s-infra

is collecting metrics looking at the logs. Took a look at the support channel and found https://signoz-community.slack.com/archives/C01HWQ1R0BC/p1723457860195989. I confirmed that if I delete the collector service, I am getting a TCP dial failure in the agent logs for the insecure port, so the configuration seems to be correct for this case. Looking for a gentle nudge in the right direction if possible, thanks for your time!

I am trying to send data from my cluster via otel agent to signoz otel collector on grpc I am seeing error in my source. My source is a default grpc otlp exporter

info	exporterhelper/queued_retry.go:423	Exporting failed. Will retry the request after interval.	{"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection termination", "interval": "32.243501486s"}

and signoz Otel collector (default grpc otlp receiver ) is throwing error as:

info	zapgrpc/zapgrpc.go:178	[transport] [server-transport 0xc000ad0b60] Closing: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"POST /opentelemetry.prot\""	{"grpc_log": true}

Has anyone else faced this error?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hi everyone. I'm evaluating SigNoz for observability and APM on a on-premise, no interne, infrastructure in production. Now I want to implement everything on a sandbox VM. After clickhouse install I did clickhouse-client -q "SELECT version()" -> 25.3.2.39 Then

clickhouse-client -q "CREATE USER signoz IDENTIFIED BY 'signoz';" 
clickhouse-client -q "GRANT ALL ON signoz_traces.* TO signoz;"
clickhouse-client -q "GRANT ALL ON signoz_logs.* TO signoz;"
clickhouse-client -q "GRANT ALL ON signoz_metrics.* TO signoz;"

clickhouse-client -q "CREATE DATABASE IF NOT EXISTS signoz_traces;"
clickhouse-client -q "CREATE DATABASE IF NOT EXISTS signoz_logs;"
clickhouse-client -q "CREATE DATABASE IF NOT EXISTS signoz_metrics;"

clickhouse-client --user signoz --password signoz

Connection ok FOr SigNoz itself, once installed (following the documentation)

sudo bash -c 'cat <<EOF > /opt/signoz/conf/systemd.env
SIGNOZ_INSTRUMENTATION_LOGS_LEVEL=info
INVITE_EMAIL_TEMPLATE=/opt/signoz/templates/invitation_email_template.html
SIGNOZ_SQLSTORE_SQLITE_PATH=/var/lib/signoz/signoz.db
SIGNOZ_WEB_ENABLED=true
SIGNOZ_WEB_DIRECTORY=/opt/signoz/web
SIGNOZ_JWT_SECRET=secret
SIGNOZ_ALERTMANAGER_PROVIDER=signoz
SIGNOZ_TELEMETRYSTORE_PROVIDER=clickhouse
SIGNOZ_TELEMETRYSTORE_CLICKHOUSE_DSN=<tcp://localhost:9000?password=signoz>
EOF'

sudo getent passwd signoz >/dev/null || sudo useradd --system --home /opt/signoz --no-create-home --user-group --shell /sbin/nologin signoz
sudo chown -R signoz:signoz /var/lib/signoz
sudo chown -R signoz:signoz /opt/signoz

sudo bash -c 'cat <<EOF > /etc/systemd/system/signoz.service
[Unit]
Description=SigNoz
Documentation=<https://signoz.io/docs>
After=clickhouse-server.service

[Service]
User=signoz
Group=signoz
Type=simple
KillMode=mixed
Restart=on-failure
WorkingDirectory=/opt/signoz
EnvironmentFile=/opt/signoz/conf/systemd.env
ExecStart=/opt/signoz/bin/signoz --config=/opt/signoz/conf/prometheus.yml --use-logs-new-schema=true --use-trace-new-schema=true

[Install]
WantedBy=multi-user.target
EOF'

I have copy pasted on the dashboard the template for hostmetrics but I got.

code: 516, message: default: Authentication failed: password is incorrect, or there is no user with such name. If you use ClickHouse Cloud, the password can be reset at <https://clickhouse.cloud/> on the settings page for the corresponding service. If you have installed ClickHouse and forgot password you can reset it in the configuration file. The password for default user is typically located at /etc/clickhouse-server/users.d/default-password.xml and deleting this file will reset the password. See also /etc/clickhouse-server/users.xml on the server where ClickHouse is installed.

I may made a typo somewhere, but I think i have followed the how-to. ANy idea here ?