Hi can someone guide me on how to make this environment selection work? https://signoz.io/blog/community-update-23/#ability-to-filter-by-deployment-environment-in-service-maps

This message was deleted.

Hi, I am running micro-services using docker compose on a Ubuntu box. Here is example docker compose.

version: '3.8'
services:
  foo:
    image: ...
    ...

  bar:
    image: ...
    ...

I want to collect logs without changing any micro-service service code. I am using

logspout

to forward log with following command. This is successfully forwarding logs.

docker run --net=host --rm --name="logspout" \
        --volume=/var/run/docker.sock:/var/run/docker.sock \
        -e PORT=90 \
        gliderlabs/logspout \
        syslog+tcp://<host>:2255

What is missing is logs are not categorised in SigNoz under their respective service names. How to configure

logspout

to send

service

name along with logs. Or is there any other log collector other than

logsspout

which can send more metadata along with logs.

Hello, i would like to setup ClickHouse in HA mode (https://signoz.io/docs/operate/clickhouse/distributed-clickhouse/#distributed-clickhouse-setup-for-signoz) with 2 ClickHouse replicas, but from what i've read (e.g here: https://github.com/ClickHouse/ClickHouse/issues/57382#issuecomment-1839223016) i would need to use replicated tables when trying to use 2 replicas, also on the page there is a info "Multiple replicas for clickhouse shards are not supported in v0.12.0 so don't change replicasCount in the clickhouse config, please follow upcoming releases to check availability of replication of clickhouse shards". I installed SigNoz with version 0.40 and would like to use 2 replicas of ClickHouse, is it possible in this version?

This message was deleted.

Hey 👋, I am here to contribute to the backend a bit. For my first task I've decided upon implementing telegram alerts (issue link). Any comments there would be appreciated. Today I setup a dev environment and had some trouble. 1. Some DB error fixed by changing the owner of

/var/lib/signoz

. I suppose this is because the make

dev-setup

was run using sudo. 2. I had a some trouble with otel-collector reaching query-service process. This took me some time to figure out but in the end I had to add a network in the docker-compose file so internal host could be reached. Also added a corresponding rule to

iptables

to allow the container to use host networking. Then finally set otel opamp config to

server_endpoint: <ws://docker.internal:4320/v1/opamp>

and now its finally working. 3. Some line numbers in the instructions are outdated. Not a big issue but perhaps we can avoid the line numbers in the instructions all together as its only a matter of time before they are outdated again. 4. Maybe consolidating the

query-service/README.md

into CONTRIBUTING.md would be helpful to setup dev environments. Anyways, I'm setup now and it is probably smooth sailing from here on out.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.