I will try to see how opentelemetry works with php. Though I am no expert in php.

If you can figure out how to instrument even in Jaeger/Zipkin format, SigNoz can ingest the data..since it uses otel-collector

Please help me with this error.

I am trying to see the positioning of Signoz. I do understand its good for small teams who are looking for open source alternative to more costlier APM solutions. However, would love to see it against Otel + Prometheus + Grafana combination.

.... asked the above question. What's the best way to answer the same?

@User Nice thought. Any particular service you think of? Would be great to have this as an issue. Would like to work on this asap

Hello everyone Anyone here who can help me with an article or source which can help me understand better about open source licenses and their basic differences

only problem I'm having is incorporating it into my Spring Boot test app ... I'm getting the following error in my logs

[otel.javaagent 2021-06-28 11:10:02:965 +0200] [grpc-default-executor-3] ERROR io.opentelemetry.exporter.otlp.metrics.OtlpGrpcMetricExporter - Failed to export metrics. Server responded with UNIMPLEMENTED. This usually means that your collector is not configured with an otlp receiver in the "pipelines" section of the configuration. Full error message: UNIMPLEMENTED: unknown service opentelemetry.proto.collector.metrics.v1.MetricsService

is there another step I'm meant to do via the UI? I don't see anywhere to add a service, and my app doesn't show up in the service map

I'll try the druid option - the clickhouse option seemed simpler for local testing, but seems broken atm?

opentelemetry-instrument python manage.py runserver --noreload
You are using Python 3.6. This version does not support timestamps with nanosecond precision and the OpenTelemetry SDK will use millisecond precision instead. Please refer to PEP 564 for more information. Please upgrade to Python 3.7 or newer to use nanosecond precision.
Instrumenting of django failed
Traceback (most recent call last):
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 81, in _load_instrumentors
    distro.load_instrumentor(entry_point, skip_dep_check=True)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/distro.py", line 63, in load_instrumentor
    instrumentor().instrument(**kwargs)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/instrumentor.py", line 106, in instrument
    **kwargs
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/django/__init__.py", line 132, in _instrument
    settings_middleware = getattr(settings, "MIDDLEWARE", [])
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/django/conf/__init__.py", line 79, in __getattr__
    self._setup(name)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/django/conf/__init__.py", line 64, in _setup
    % (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting MIDDLEWARE, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
Failed to auto initialize opentelemetry
Traceback (most recent call last):
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 111, in initialize
    _load_instrumentors(distro)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 85, in _load_instrumentors
    raise exc
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/auto_instrumentation/sitecustomize.py", line 81, in _load_instrumentors
    distro.load_instrumentor(entry_point, skip_dep_check=True)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/distro.py", line 63, in load_instrumentor
    instrumentor().instrument(**kwargs)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/instrumentor.py", line 106, in instrument
    **kwargs
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/opentelemetry/instrumentation/django/__init__.py", line 132, in _instrument
    settings_middleware = getattr(settings, "MIDDLEWARE", [])
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/django/conf/__init__.py", line 79, in __getattr__
    self._setup(name)
  File "/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/django/conf/__init__.py", line 64, in _setup
    % (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting MIDDLEWARE, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
/home/cmkishores/.virtualenvs/entri/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <<http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>>.
  """)
Performing system checks...

I hope someone can share an insight. 🙂

please give me container registry repo access for helm operator

I'm trying to connect my django app to signoz. In my docker for running django, server starts with

command: ['opentelemetry-instrument', 'python', 'manage.py', 'runserver', '0.0.0.0:80', '--noreload']

This runs successfully. I have an env file with

OTEL_RESOURCE_ATTRIBUTES=service.name=pythonApp 
OTEL_METRICS_EXPORTER=none
OTEL_EXPORTER_OTLP_ENDPOINT="<http://localhost:4317>"

But when I check the signoz dashboard, my app does not show up

hey @User have you checked the python instrumentation docs - https://signoz.io/docs/instrumentation/python/

Can I set single Centralized SigNoz APM for multiple kubernetes cluster ? e.g. Single SigNoz for Dev , Test and Stage Cluster ? Also what is resource requirement for SigNoz in kubernetes ?

Is it possible to use signoz with a DB other that clickhouse? if yes, what are supported and how can I use them instead of click house?

Hey guys, I’m trying to connect my tomcat to signoz, followed the steps in https://signoz.io/docs/instrumentation/java/, but I didn’t see my app in the dashboard, could anyone please help?

<!here> Hello Everyone, I am struggling to instrument golang application to signoz. Here is some basic info about my application. 1. All the go code compiled and prepared as binary. 2. now using

make

command with

MakeFile

spec, we are preparing this go binary into an RPM file which is installable on any cent os. 3. after installing RPM file

rpm -i goapp.rpm

it will create service in systemd and available to use

systemctl

to start/stop the service. 4. i used to start my go app using

systemctl start svfileserver

svfileserver is the name of the service (go application) Now please help to instrument svfileserver service to signoz.

Hello guys I need information about the API so that I can get some custom data from front end

Hi, Have small issue In general i rewrote the query service with some table changes to improve performance(only for clickhouse, using fiber as the web framework) All works well, however, i’ve encountered some issue: Trace view might get “broken” if one of the traces is missing, on my case, i had a trace which was set as CHILD_OF, however its parent span was missing, so trace view did not show all the traces, only the total request time, while response had 34 spans available in the specific trace Few ways to handle it: 1. On backend(query service) if some span link is missing, the set its references to empty array, and reorder traces accordingly if there is some gap 2. On frontend, add some note trace is missing, but display the rest of traces The optimizations i’ve added to query service: 1. Use MV with aggregated data per service, to display the metrics page faster 2. Retain only problematic traces(traces with status code >=400, or duration greater the X), so data could be retained for longer period I want to add some SLA report with comparison between days/weeks/months, in my case it will generate CSV(and send to mail) as FE is not something Im familiarbwith

Hello, team! I deployed signoz on Digitalocean kubernetes cluster and I want to monitor my nodejs appication, I followed this reference https://signoz.io/opentelemetry/nodejs/, but I am facing below error

Invalid configuration: access token missing, must be set when reporting to <https://ingest.lightstep.com/traces/otlp/v0.6>. Set LS_ACCESS_TOKEN env var or configure token in code
LightstepConfigurationError: Invalid configuration: access token missing, must be set when reporting to <https://ingest.lightstep.com/traces/otlp/v0.6>. Set LS_ACCESS_TOKEN env var or configure token in code
    at /node/node_modules/lightstep-opentelemetry-launcher-node/build/src/lightstep-opentelemetry-launcher-node.js:128:15
    at validateToken (/node/node_modules/lightstep-opentelemetry-launcher-node/build/src/lightstep-opentelemetry-launcher-node.js:147:9)
    at validateConfiguration (/node/node_modules/lightstep-opentelemetry-launcher-node/build/src/lightstep-opentelemetry-launcher-node.js:136:5)
    at Object.configureOpenTelemetry (/node/node_modules/lightstep-opentelemetry-launcher-node/build/src/lightstep-opentelemetry-launcher-node.js:44:5)
    at Object.<anonymous> (/node/server_init.js:6:23)
    at Module._compile (internal/modules/cjs/loader.js:1133:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
    at Module.load (internal/modules/cjs/loader.js:977:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Object.<anonymous> (/usr/local/lib/node_modules/pm2/lib/ProcessContainerFork.js:33:23)

can any one knows how to setup signoz in amazon ec2 server

i wonder if there is a major difference if i want to use the solution with jboss

Though it seems you should use JAVA_OPTS instead of CATALINA_OPTS for JBOsshttps://stackoverflow.com/a/11222367

Greetings. I am testing various java APMs so my docker setup has a lot of allocated ports and I have run into a number of port conflicts deploying SigNoz. Does anyone have a cheat sheet (or script) that will help me work my way through all the configuration files to get a unique set of ports setup? thanks.

all open telemetry modules are installed

Hi. This is Lakshyajit. We have been getting a particular error in our kafka + druid setup of signoz today. The error is as follows: 2021-10-18T07:44:56.354Z    [31mERROR[0m    druidQuery/mysql-query.go:427    &{2021-10-18T07:29:43.095Z 2021-10-18T07:34:43.095Z 300 2021-10-18 07:29:43.095 +0000 UTC 2021-10-18 07:34:43.095 +0000 UTC} 400 Bad Request: {"error":"Plan validation failed","errorMessage":"org.apache.calcite.runtime.CalciteContextException: From line 1, column 164 to line 1, column 178: Object 'flattened_spans' not found","errorClass":"org.apache.calcite.tools.ValidationException","host":null} P.S. The signoz server is running on a GKE cluster using Helm. Any help would be appreciated. Thanks.

Hi @all i just tryed to install kafka+druid dependencies on my windows by docker compose. When i go to the sub dir where the yaml are placed and i run my docker compose up command i recieve the following error :

Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/run/desktop/mnt/host/c/Users/Davide/Development/Signoz/signoz/deploy/docker/druid-kafka-setup/nginx-config.conf" to rootfs at "/etc/nginx/conf.d/default.conf" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Hi guys , what happened to these two packages in the getting started guide ? "go.opentelemetry.io/otel/exporters/otlp"     "go.opentelemetry.io/otel/exporters/otlp/otlpgrpc"