This message was deleted.

Hello Team, I am trying to change the retention period of Traces but the process has been stuck for the past 5-6 days now. It just says

Your last call to change retention period to 7 days is pending. This may take some time.

Can you please help with this?

I installed latest signoz chart using helm, and otel-collector is not stuck in Init

apm-signoz-otel-collector-9cccf7889-8pzg7            0/1     Init:0/1    0          110m

These are the pod logs

❯ k logs -n platform -f apm-signoz-otel-collector-9cccf7889-8pzg7                          
Defaulted container "collector" out of: collector, apm-signoz-otel-collector-migrate-init (init)
Error from server (BadRequest): container "collector" in pod "apm-signoz-otel-collector-9cccf7889-8pzg7" is waiting to start: PodInitializing

This message was deleted.

Hi, I'm trying to run SigNoz locally using the official Docker Compose installation steps https://signoz.io/docs/install/docker/#install-signoz-using-docker-compose however when I try and start it I get an error telling me

no service selected

, am I missing a step? I'm running on latest macOS. Thanks 🙏

This message was deleted.

Hi team- I'm experimenting with signoz right now, and trying to get it stood up in k8s using the helm chart. We already use clickhouse, so I was seeing if I could just attach to that installation rather than having signoz spin up a new one. After some adjustments, I've gotten many things to spin up and run correctly, including the schema migration tool. However, the query service raises an error:

error connecting to primary db: code: 516, message: signoz: Authentication failed: password is incorrect, or there is no user with such name.

More details in 🧵 ... any help is greatly appreciated! UPDATE: fixed ... 1. quick workaround: don't use

+

chars in the password for credentials signoz uses to connect to the external instance. specifically the query service uses a URL format, and passwords are not properly url-encoded, so `+`'s turn into spaces according to the url. 2. https://github.com/SigNoz/charts/issues/473

This message was deleted.

Hi guys, I'm using Vector.dev to forward logs from my app (hosted on Fly.io) to self-hosted Signoz in some VPS. My

vector.toml

is very simple:

[sinks.signoz]
type = "http"
uri = "${PROD_URL:-<http://localhost:8082>}"
inputs = ["hotel"]
encoding.codec = "json"

I followed https://signoz.io/docs/userguide/send-logs-http/ to the dot, except I'm sending the JSON one by one because I don't know how to send "batch" (issue here: https://github.com/vectordotdev/vector/discussions/20425). My problem: Signoz's HTTP endpoint returns 400 if the log comes faster than once a second (I'm exaggerating a bit), which renders it useless. Where can I configure Signoz to allow higher throughput? Error log in Vector (to show you the 400 error):

2024-05-04T14:20:29.727353Z ERROR sink{component_kind="sink" component_id=signoz component_type=http}:request{request_id=1}: vector::sinks::util::retries: Not retriable; dropping the request. reason="Http status: 400 Bad Request" internal_log_rate_limit=true

I know my Vector setup works because it works when I change the sink to e.g., Longtail. Also, if I send request one by one using Postman, Signoz works.

This message was deleted.