Need help with below error: the query-service is not getting up

Hello, New to the space. I was wondering if it would be possible to get the plain k8s manifest for signoz stack ? Thank you

Hi I have auto instrumented my grpc go lang application by adding interceptors as done here : https://github.com/open-telemetry/opentelemetry-go/blob/example/grpc/v0.10.0/example/grpc/server/main.go I also used this third party library to instrument by database metrics : https://github.com/signalfx/splunk-otel-go/tree/main/instrumentation/github.com/jinzhu/gorm/splunkgorm However for a single request I am seeing two traces created.. one for application and for database. Is there a way to have the same trace id associated with both app and database to get a unified view?

Question asked by one of our community member: Is it possible to use core opentelemetry collector agents write to signoz exporter instead of using custom collector provided by signoz? cc: @User @User

Hi! I installed signoz on windows kubernetes, I can access the dashboard...I wante to test the ASPNetCore sample...But I can't make it work. I followed the troubleshooting guide and there seems there are no problems.

Hi Team, I have installed OpenTelemetry with SigNoz. Signoz is capturing everything from my application except MS-SQL database. I want to see the query related information also for every request we are getting. Setup is on Ubantu 20 machine. Application using nest js and "mssql": "^6.0.1".

Hi Team, I have installed OpenTelemetry with SigNoz and it was working fine previously. Today, I am getting exceptions in my tomcat (catalina logs) but Signoz is running perfectly. I am attaching the exception. Can someone help me? It's printing on a short interval (may be due to corn jobs running) which causes my server to slow down. Exception: ERROR io.opentelemetry.exporter.otlp.internal.grpc.OkHttpGrpcExporter - Failed to export spans. The request could not be executed. Full error message: timeout

bash-3.2$ docker run -it --rm signoz/troubleshoot checkEndpoint --endpoint=localhost:4317 2022-03-03T14:48:06.681Z INFO troubleshoot/main.go:28 STARTING! 2022-03-03T14:48:06.687Z INFO checkEndpoint/checkEndpoint.go:41 checking reachability of SigNoz endpoint Error: not able to send data to SigNoz endpoint ... rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:4317: connect: connection refused"

I raised PR https://github.com/SigNoz/signoz/pull/815 could not pass a CI check, can you please help me with it ?

I tried running query service using

go run main.go

(inside

pkg/query-service

), but for adding new dependencies like

viper

, I had to pin its version like

go get <http://github.com/spf13/viper@v1.0.0|github.com/spf13/viper@v1.0.0>

to make it work. Go version:

v1.14.7

On using

go mod tidy

or

go build

, dependencies seem to collide. When I add new dependencies like

viper

to the project, the Docker build (

make build-query-service-amd64

) and locally building query service fails. Full error stacktrace:

./../../../.gvm/pkgsets/go1.14.7/global/pkg/mod/github.com/!sig!noz/prometheus@v1.9.68/discovery/consul/consul.go:27:2: ambiguous import: found package <http://github.com/hashicorp/consul/api|github.com/hashicorp/consul/api> in multiple modules:
        <http://github.com/hashicorp/consul|github.com/hashicorp/consul> v1.1.1-0.20180615161029-bed22a81e9fd (/home/user/.gvm/pkgsets/go1.14.7/global/pkg/mod/github.com/hashicorp/consul@v1.1.1-0.20180615161029-bed22a81e9fd/api)
        <http://github.com/hashicorp/consul/api|github.com/hashicorp/consul/api> v1.12.0 (/home/user/.gvm/pkgsets/go1.14.7/global/pkg/mod/github.com/hashicorp/consul/api@v1.12.0)

The problem is in

<http://github.com/signoz/prometheus|github.com/signoz/prometheus>

, it seems. I replicated the same issue in an isolated environment (Docker) and used multiple go versions (1.14, 1.17) using

gvm

, but the issue still persists.

Is opentelemetry-instrument with django expected to only record web requests with no breakdown of function calls nor DB calls? I'm using the automatic instrumentation run command as described [here](https://signoz.io/docs/instrumentation/python#instrumenting-django-applications). Is there any way to get more information? See example Trace. I also tried the django-sample but I was unable to get it working. Nothing shows up when trying a Python virtual environment without Docker. The docker image for it appears to not support x86. There is also a typo on the readme

signoz/sample-django:latest1

there should not be a 1. In addition, it is not safe to assume

host.docker.internal

will resolve, though fixing these issues results in an message about not having the x86 image. I do not have any arm hardware to test on.

Hi All, While installing the application it is asking for password, please check and suggest.

Hi team, I am recording exceptions (NodeJs) using recordEception and setStatus helper, but I am unable to get those "metadata" in UI. I can see the span status code is set to error but it doesn't contain any information about error (message or exception stack trace). Is there a way to enrich span with this information?

This message was deleted.

In the default SigNoz application, I don't see any dashboards as shown in the documentation? Is there any setup needed. I wan to add CPU utilisation metrics dashboards

Hi Guys, My name is Ofir, I'm a consultant Cloud-Architect and new to this slack community I've been experimenting with SigNoz to get OpenTelemetric on an AWS EKS Cluster, the cluster is using Fargate nodes only and all pods fail to go live and remain pending because of the scheduler not being able to schedule them with the following error:

Warning  FailedScheduling  4m15s (x225 over 4h9m)  default-scheduler  0/5 nodes are available: 5 node(s) had taint {<http://eks.amazonaws.com/compute-type|eks.amazonaws.com/compute-type>: fargate}, that the pod didn't tolerate.

I was wondering if there is a different helm configuration to meet fargate configuration (or any additional step to overcome this issue) Thanks in advance for any assistance

Hi i just started using signoz yesterday. It was working as intended. However this morning im getting this message? Can anyone help me in further troubleshooting this message?

Hi! I just started integrating SigNoz in our application, backend integration for golang & java based services worked smoothly, but facing issue with angular inteceptor for opentelemetry. It is showing connection reset error. Any direction to solve this would be highly appreciated.

Has anyone done benchmarking on OTLP receiver ie performance comparison for http vs grpc. Found this link but no numbers : https://github.com/open-telemetry/opentelemetry-collector/discussions/4102

Hello Team, My name is Srinjoy , i had setup a new signoz deployment using the default values and helm on my kubernetes cluster next i deployed the otel collector agent to collect metrics from pods and nodes following https://signoz.io/docs/tutorial/kubernetes-infra-metrics/ But i could not see the metrics anywhere on the frontend ui, Also plot metric in signoz ui instruction doc is empty https://signoz.io/docs/userguide/metrics-dashboard/ 1. I checked all signoz pods are up and running on my cluster 2. I added the endpoint for my signoz application in the collector agent yaml 3. I also checked that each node is running a otel collector agent Am i missing something.

Hi There :) I am trying to get Signoz work to get see if it could fit us. I could easily install it on minikube but I have a lot of difficulty install it on EKS fargate. My next move is to add an EC2 node to our fargate cluster (not ideal in the long run but ok solution for now) and "force" Signoz helm installation to "land" on the EC2 node. So far without success but I believe I will succeed at some point. Do you know if there is a more native support for EKS Fargate? Thanks!

Hi #support Team, I am starting to explore SigNoz as our APM. Few are my questions. • How to secure my APM server - otel collector? My Otel collector will be publicly hosted and need to have atleast Basic Auth. • Also, in wanted to add custom tags to my agent. Something like, -Dotel.resource.attributes=service.name=myapp,my.tag=123abc ◦ I am able to get service.name mapped properly but i am unable to see my custom attributes like "my.tag" - in Jaeger, I can find the same as tags. In Signoz, where can i find them. • For Service Map - can i group - some services and view their map. Else when number of services increase - it will be hard to read. Please clarify on these. Thanks!

Hello team! I've installed signoz in my kubernetes cluster using the standart documentation with helm. I can send the data using port fowarding but i cant using ingress, so the error is on the redirecting. Can anyone help me?

I am getting this blank screen quite a few times upon using the UI for various cases. Also the service map does not show map on selecting from dropdown. Is this known?

Hello, #support I have one issue and one question: My issue: I installed Signoz using a standalone docker container in a small t3.nano instance. (didn't get to remove the default project) and my instance CPU went through the roof 99% and result in crashing my instance. So, here am wondering what are the recommended instance size or resource. My issue: I have installed Signoz via a standalone docker container and could see the dashboard in

<http://my-ip:3301>

however, now when it comes to creating Instrumenting for my FastAPI application I get confused. • port 3301: This port to access my signoz dashboard (in the server where signoz is running) - as per the installation page here - https://signoz.io/docs/install/docker • port 4317: in the Instrumenting a sample FastAPI application with OpenTelemetry page - https://signoz.io/docs/instrumentation/fastapi/ the following command:

OTEL_RESOURCE_ATTRIBUTES=service.name=<service_name> \OTEL_EXPORTER_OTLP_ENDPOINT="http://<IP of SigNoz>:4317" \

opentelemetry-instrument uvicorn main:app --host localhost --port 5002

1- Should port 4317 be open in the instance where signoz is running (like using a security group to allow access) 2- is this port just for OTEL data sharing? Sorry if am missing something here, am not a DevOps guy and will appreciate any clarification if am confused about something here

Hi I am using below method to get the trace provider :

func getTraceProvider(svcName string, server string) (*sdkTrace.TracerProvider, error) {
	env, _ := cfg.GetEnvironment()
	provider := sdkTrace.NewTracerProvider(
		sdkTrace.WithResource(sdkResource.NewWithAttributes(
			semconv.SchemaURL,
			semconv.DeploymentEnvironmentKey.String(env),
			semconv.ServiceNameKey.String(svcName),
			semconv.ServiceNamespaceKey.String(server),
		)),
	)
	otel.SetTracerProvider(provider)
	otel.SetTextMapPropagator(propagation.TraceContext{})
	return provider, nil
}

However I do not see DeploymentEnvironmentKey, SchemaURL, etc on signoz dashboard anywhere. I verified with std out exporter and these values are being passed.

I am trying to use signoz for a POC and after some time of running signoz running into following error, this has happened multiple times now since the last two days, had to restart the services to get it working, this is a critical factor in deciding if we want to proceed with signoz or not, please help at the earliest

I'm using the docker-compose (clickhouse) setup. There is an error in the logs every 5 seconds:

otel-collector_1          | 2022-03-22T08:51:28.780Z	info	service/collector.go:124	Everything is ready. Begin running and processing data.
otel-collector_1          | time="2022-03-22T08:51:28Z" level=error msg="invalid character '\\x06' in string literal" component=clickhouse
otel-collector_1          | time="2022-03-22T08:51:33Z" level=error msg="invalid character '\\x06' in string literal" component=clickhouse
otel-collector_1          | time="2022-03-22T08:51:38Z" level=error msg="invalid character '\\x06' in string literal" component=clickhouse
otel-collector_1          | time="2022-03-22T08:51:43Z" level=error msg="invalid character '\\x06' in string literal" component=clickhouse
otel-collector_1          | time="2022-03-22T08:51:48Z" level=error msg="invalid character '\\x06' in string literal" component=clickhouse

How can I debug this? Or can I ignore this? Unfortunately the app is behaving strange (the /trace page is working, but if I click on a trace the page is blank).

Hi #support Does Signoz support capturing frontend traces using http? Is there any working example available? But in Jaeger there is an option to capture Frontend UI traces via HTTP protocol by adding

api/traces

but the same did not work with signoz