https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
s
It comes from the instrumentation done by the user.
r
i have this issue too
s
What’s the issue? You could configure the service.name in SDK number of ways include 
OTEL_SERVICE_NAME
, 
OTEL_RESOURCE_ATTRIBUTES=...,service.name=xx,..
and manually adding it when initialising the telemetry pipelines.
r
i already add instrument in nodejs simple apps. but its not discoverable by signoz
logs only
see-ip-address@0.0.0 start
node ./bin/www tracing.js
:ffff127.0.0.1 GET / 200 43.658 ms - 1499 GET /stylesheets/style.css 200 4.175 ms - 111 GET /favicon.ico 404 2.329 ms - 823 :ffff127.0.0.1
@Pranay @Srikanth Chekuri any help?
update logs
see-ip-address@0.0.0 start
node -r ./tracing.js ./bin/www
Tracing initialized :ffff127.0.0.1 GET / 200 88.746 ms - 1500 GET /stylesheets/style.css 200 26.111 ms - 111 GET /favicon.ico 404 6.920 ms - 960 :ffff127.0.0.1 GET / 200 4.103 ms - 1624 GET /stylesheets/style.css 304 3.241 ms - - :ffff127.0.0.1
s
That’s a different issue from what the original author talks about. What’s there in the 
./bin/www
. What framework and versions are you using? Please share more context
r
express Js
logs in pod already has tracing initialized
in deploy already add - env: - name: service_name value: hello-svc
i use signoz helm chart in gcp kubernetes
i do --set 
frontend.service.type=LoadBalancer
FE version is 0.13.0
s
Can you try running it locally with the console exporter and confirm if the instrumentation is working in the first place? https://signoz.io/docs/faqs/troubleshooting/#how-do-i-know-if-signoz-is-accessible-from-my-application
r
can you give me link to add instrument lastest doc?
s
yes that should be enough
r
but the service is not discoverable
5 Views
Open in Slack
PreviousNext
Powered by