This message was deleted.

3 in

otelcol_exporter_sent_spans

is from Troubleshooting binary.

@User 1. Did you hit any apis of the application? Only then trace data will be generated. 2. Did you compare to or tried running https://github.com/SigNoz/sample-django?

Thanks @User for your quick response. 1. Yes I did hit the api via browser. 2. I did ran the sample-django application but when I first tried SigNoz. And I did it with standalone docker image(all in one).

ok...do the application logs show some error other than

Overriding of current TracerProvider is not allowed

?

I was able to get rid of

Overriding of current TracerProvider is not allowed

by changing _`OTEL_METRICS_EXPORTER=none DJANGO_SETTINGS_MODULE=shopfloor.settings OTEL_RESOURCE_ATTRIBUTES=service.name=stitch OTEL_EXPORTER_OTLP_ENDPOINT="http://signoz-uat-otel-collector.platform.svc.cluster.local:4317" opentelemetry-instrument gunicorn shopfloor.wsgi -c gunicorn.config.py --bind 0.0.0.0:8000`_ to

gunicorn shopfloor.wsgi -c gunicorn.config.py --bind 0.0.0.0:8000

It seems Django specific configuration is not allowed with gunicorn specific configuration. Documentaion needs to clarify upon it. Two more thing that is still unclear :- 1. use of _`OTEL_METRICS_EXPORTER=none`_ 2. should we use

http://

with

OTEL_ENDPOINT

or not as troubleshooting binary doesn't allow it but application doesn't throw any error. Still won't able to get anything to backend.

root@django-backend-deployment-bb8875d7c-mmbpc:/app# gunicorn shopfloor.wsgi -c gunicorn.config.py --bind 0.0.0.0:8000
[2022-02-23 08:53:24 +0000] [31] [INFO] Starting gunicorn 19.9.0
[2022-02-23 08:53:24 +0000] [31] [INFO] Listening at: <http://0.0.0.0:8000> (31)
[2022-02-23 08:53:24 +0000] [31] [INFO] Using worker: sync
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
[2022-02-23 08:53:24 +0000] [33] [INFO] Booting worker with pid: 33
[2022-02-23 08:53:24 +0000] [33] [INFO] Worker spawned (pid: 33)
[2022-02-23 08:56:11 +0000] [31] [CRITICAL] WORKER TIMEOUT (pid:33)
[2022-02-23 08:56:11 +0000] [33] [INFO] Worker exiting (pid: 33)
[2022-02-23 08:56:12 +0000] [42] [INFO] Booting worker with pid: 42
[2022-02-23 08:56:12 +0000] [42] [INFO] Worker spawned (pid: 42)
[2022-02-23 08:56:52 +0000] [31] [CRITICAL] WORKER TIMEOUT (pid:42)
[2022-02-23 08:56:52 +0000] [42] [INFO] Worker exiting (pid: 42)
[2022-02-23 08:56:52 +0000] [64] [INFO] Booting worker with pid: 64
[2022-02-23 08:56:52 +0000] [64] [INFO] Worker spawned (pid: 64)
[2022-02-23 09:00:27 +0000] [31] [CRITICAL] WORKER TIMEOUT (pid:64)
[2022-02-23 09:00:27 +0000] [64] [INFO] Worker exiting (pid: 64)
[2022-02-23 09:00:28 +0000] [93] [INFO] Booting worker with pid: 93
[2022-02-23 09:00:28 +0000] [93] [INFO] Worker spawned (pid: 93)

getting this.

I see you removed all env vars, that won't instrument the applications now. Earlier was correct.

1. use of _`OTEL_METRICS_EXPORTER=none`_

It tells not to export metrics. It is not needed now as SigNoz can ingest metrics too now. Anyways, I don't think it will affect anything.