https://signoz.io
Join Slack
How can I set a limit to disk space usage for self hosted Signoz?
s

Stefan Schneider

about 1 year ago
How can I set a limit to disk space usage for self hosted Signoz?
s
c
+3
  • 5
  • 14
  • 164
This message was deleted.
s

Slackbot

almost 2 years ago
This message was deleted.
s
v
s
  • 3
  • 3
  • 161
This message was deleted.
s

Slackbot

almost 2 years ago
This message was deleted.
s
s
+2
  • 4
  • 5
  • 160
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
s
q
  • 3
  • 2
  • 159
Hi All I'm in the process of setting up SigNoz using Docker Compose and I've pulled the `docker-com...
m

Murat Kuru

about 1 year ago
Hi All I'm in the process of setting up SigNoz using Docker Compose and I've pulled the
docker-compose.yaml
from [this link](https://github.com/SigNoz/signoz/blob/develop/deploy/docker/clickhouse-setup/docker-compose.yaml). However, as I was reviewing the file, I noticed that it references several outdated images, some of which have critical vulnerabilities. For instance, the image
signoz/locust:1.2.3
is specified, but the latest version available is
signoz/locust:2.24.1
. Could someone shed some light on why these older versions are being used and if there are plans to update them? Alternatively, would it be advisable to simply replace them with the latest versions to ensure security and compatibility? Here's a list of the outdated images mentioned in the YAML file: -
signoz/frontend:0.38.2
-
gliderlabs/logspout:v3.2.14
-
signoz/alertmanager:0.23.4
-
signoz/query-service:0.38.2
-
signoz/signoz-otel-collector:0.88.11
-
clickhouse/clickhouse-server:23.11.1-alpine
-
signoz/locust:1.2.3
(mentioned above) -
bitnami/zookeeper:3.7.1
-
jaegertracing/example-hotrod:1.30
Looking forward to your insights on this.
m
p
s
  • 3
  • 4
  • 158
in the signoz k8s chart, how do i run the `job/signoz-schema-migrator-upgrade` again? it seems it d...
h

hans

11 months ago
in the signoz k8s chart, how do i run the
job/signoz-schema-migrator-upgrade
again? it seems it didnt run properly and
kubectl create job signoz-schema-migrator-upgrade-lolol --from=job/signoz-schema-migrator-upgrade
is not working, giving
error: unknown object type *v1.Job
h
a
p
  • 3
  • 63
  • 153
28m Warning FailedToUpdateEndpoint endpoints/my-release-k8s-infra-otel-agent ...
a

Anil Kumar Bandrapalli

about 1 year ago
28m Warning FailedToUpdateEndpoint endpoints/my-release-k8s-infra-otel-agent Failed to update endpoint platform/my-release-k8s-infra-otel-agent: Operation cannot be fulfilled on endpoints "my-release-k8s-infra-otel-agent": the object has been modified; please apply your changes to the latest version and try again
a
s
+2
  • 4
  • 25
  • 153
This message was deleted.
s

Slackbot

over 2 years ago
This message was deleted.
s
a
+2
  • 4
  • 11
  • 153
is there a way to send traces to signoz from HTTP API? my use case is that I want to check end-to-en...
d

Dhruv garg

about 1 year ago
is there a way to send traces to signoz from HTTP API? my use case is that I want to check end-to-end latency from FE mobile applications. so FE will send time taken and API name from FE, and then BE will send to signoz using a HTTP API
d
s
  • 2
  • 16
  • 152
This message was deleted.
s

Slackbot

almost 2 years ago
This message was deleted.
s
s
  • 2
  • 1
  • 150
Previous101112Next

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