https://signoz.io
Join Slack
Hi team, is there an instruction about integrate for React Native applications to collect logs/metri...
h

Herb He

about 1 year ago
Hi team, is there an instruction about integrate for React Native applications to collect logs/metrics from mobile?
h
s
  • 2
  • 2
  • 167
Hi Team, Getting this below error while installing, please help me to fix this error. ```helm --nam...
s

surya prakash

over 1 year ago
Hi Team, Getting this below error while installing, please help me to fix this error.
helm --namespace platform install my-release signoz/signoz -f override-values.yaml
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/path/updatedkc.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/path/updatedkc.yaml
coalesce.go:175: warning: skipped value for zookeeper.initContainers: Not a table.
Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condition
s
n
p
  • 3
  • 12
  • 167
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
p
+2
  • 4
  • 21
  • 167
Hello, my schema migrator seems to contiiously fail lately with the following errors ```{"L":"info"...
m

Matti

12 months ago
Hello, my schema migrator seems to contiiously fail lately with the following errors
{"L":"info","timestamp":"2024-12-16T12:21:24.682Z","C":"schema_migrator/manager.go:393","M":"Waiting for mutations to be completed","count":1,"host":"10.244.1.54:9000"}
{"L":"info","timestamp":"2024-12-16T12:21:24.682Z","C":"schema_migrator/manager.go:395","M":"Mutation details","database":"signoz_logs","table":"schema_migrations_v2","command":"UPDATE status = 'finished', error = '', updated_at = '2024-12-16 12:15:13' WHERE migration_id = 4","mutation_id":"0000000003","latest_fail_reason":""}
{"L":"info","timestamp":"2024-12-16T12:22:31.353Z","C":"schema_migrator/manager.go:393","M":"Waiting for mutations to be completed","count":1,"host":"10.244.1.54:9000"}
{"L":"info","timestamp":"2024-12-16T12:22:31.353Z","C":"schema_migrator/manager.go:395","M":"Mutation details","database":"signoz_logs","table":"schema_migrations_v2","command":"UPDATE status = 'finished', error = '', updated_at = '2024-12-16 12:15:13' WHERE migration_id = 4","mutation_id":"0000000003","latest_fail_reason":""}
m
s
  • 2
  • 58
  • 165
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
v
s
  • 3
  • 3
  • 163
This message was deleted.
s

Slackbot

almost 3 years ago
This message was deleted.
✅ 1
s
p
+2
  • 4
  • 50
  • 162
Hi, Retention period seems to have reset to default values for some reason. We have set Retention P...
n

Noel McGrath

over 1 year ago
Hi, Retention period seems to have reset to default values for some reason. We have set Retention Period following docs @ https://signoz.io/docs/userguide/retention-period/ We set this months ago when we initially installed Signoz as it is recommended to set retention period early in the lifecycle of the platform. In sqlite signoz.db we can see the values: 54 c2da421ae3ae4c1197e0b7ee05377176 2024-03-28 133806.07271329+00:00 2024-03-28 133806.456254169+00:00 signoz_metrics.samples_v2 31104000 604800 success After 7 days(604800) move to S3 cold storage for 1 year(31104000). We have done this for Metrics, Traces and Logs. Since this time(back in March) we have done a number of upgrades of SigNoz and have just noticed there is a change to our Metrics retention period. It is now showing as 1 month and no cold storage setting. See attached image What would have caused this to have changed and why did it only do it for Metrics and not all(Traces and Logs also)? Also we now have months of metrics data, will there be an issue with us changing the retention now?
n
s
  • 2
  • 13
  • 160
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
s
q
  • 3
  • 2
  • 160
This message was deleted.
s

Slackbot

about 3 years ago
This message was deleted.
s
a
+2
  • 4
  • 11
  • 158
Hi, i am trying to run signoz in an lxc container. When i start the containers, the "signoz-clickhou...
s

Simon Voßmann

over 1 year ago
Hi, i am trying to run signoz in an lxc container. When i start the containers, the "signoz-clickhouse" container fails to start with:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 6: operation not permitted: unknown
i dont really understand why this is happening, as docker itself is running just fine, and other docker-container run just fin on this configuration. Can someone tell me what i am doing wrong?
s
s
  • 2
  • 1
  • 157
Previous131415Next

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by