Hello dumb question also in the self-hosted SigNoz...
# support
e
Hello dumb question also in the self-hosted SigNoz, to run the application we need to call
node -r ./tracing.js app.js
. Could we avoid calling node -r ./tracing.js but instead just run the app.js? Should I just require tracing.js in app.js?
Also, does the OTel Collector binary - No Code Automatic Instrumentation work for Self-hosted? I dont seem to make the app run with this. I am confused. But if we have the tracing it is working.
Also I would like to suggest that fix the A.I chat because it's not clearly reading the knowledge base. It consistently tells me that No Code Automatic Instrumentation can work for self-hosted when clearly the no code is under the SigNoz Cloud implementation. UNLESS correct me or clearly there's a workaround for no code will work on the self-hosted because for this one because clearly it was stated in the documentation, "Send traces via OTel Collector binary - No Code Automatic Instrumentation OTel Collector binary helps to collect logs, hostmetrics, resource and infra attributes. It is recommended to install Otel Collector binary to collect and send traces to SigNoz cloud." Thanks!
h
What environment are you self-hosting Signoz in? Let's say it's k8s, then the Signoz chart installs a SigNoz Collector which is a modified OTel Collector that inserts into Clickhouse. If you then use the OpenTelemetry Operator, it will inject
NODE_OPTIONS
into your containers to load
tracing.js
. You would also need to set the env-vars that point this towards the Signoz Collector. Some operator configurations can also create a sidecar container in your pods that runs a standard OTel Collector that can have a custom pipeline. If you're not using the Operator, but just the Auto-Instrumentation libraries, env-vars are still an alternative to changing your app's invocation command / start script. More details on your self-hosting environment (notice the sheer amount of combinations) will make it easier for support to guide you.