This message was deleted.

Good morning! I'm testing signoz localhost, trying to send traces from dotnet. My SigNoz local installation using docker works fine, and the sample apps that send traces are also working fine. My app uses docker and I added the

no-code autoinstrumentation

but it seems like it's not connecting to local signoz. Using libraries is not desirable at this moment, as it would imply a general upgrade of dependencies. What else can I try?

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.

yesterday my all the containers are running fine, but after 24 hours i check the containers, some containers are down automatically.

Hello, I am working on setting up a dashboard using Signoz. I have question about metric queries in the builder. The autocomplete feature for suggesting metric names is very useful. However, it seems to take a long time to suggest metric names, longer than I expected. Curious about why this takes so long, I looked into the query-service related API and the ClickHouse metric database, and found out that the following query is being used: query = fmt.Sprintf("SELECT metric_name, type, is_monotonic, temporality FROM %s.%s WHERE metric_name ILIKE $1 GROUP BY metric_name, type, is_monotonic, temporality", signozMetricDBName, signozTSTableNameV41Day) It takes more than 10 seconds to retrieve the metric names, so I suspect it might be related to indexing. Is there any way to improve the query performance?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.