https://signoz.io
Join Slack
Hello Team, we are having issues. We are using NestJS Otel. We are activating this tracer from NestJ...
# support
t
Hello Team, we are having issues. We are using NestJS Otel. We are activating this tracer from NestJS, but the Service Name remains CLIENT, the namespace remains HSUITE-ENTERPRISE. Maybe because those were the first values in the first try we did? And if so, how do we delete the old data that is still showing? Even if we start a clean docker, its like open telemetry from NestJS sends data from last week which was the time it was installed. Any help please? we are going crazy
c
Hey @Tomachi ! Can you checkout this doc for instrumentation and see if you’re missing something - https://signoz.io/docs/instrumentation/nestjs/
t
It all works, but the problem is that does not get the new service name and namespace. and even if i clean up dockers and such it keeps getting the data from last week. how can we start from zero and do a full cleanse?? Where is this data stored?
c
I think you can try removing all the docker containers and images related to SigNoz. @Prashant Shahi can you help here ?
t
yeah it didnt work removing the dockers
so we managed to delete data, however the service name still remains 'client'
its like nestJS Otel is not considering the resource with all the naming
we even tried following your guide of signoz local and it is not working
ok, so we had to add serviceName, but regardless of this, why does the resource not work??
Also, why do you guys dont use simplespanProcessor or batch span processor??? and only passed as traceExporter?
c
Were you able to resolve the issue ?
t
only partially, we cant set the namespace
we dont understand where it needs to be set
hello, any update for this?
c
@Prashant Shahi @Srikanth Chekuri can anyone of you help here please
17 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by