This message was deleted.

any update on this ? as i tried so many ways but couldn't find the resolution. i followed the tutorial as well

What issues are you facing? Do you see any errors on node js app?

no issue from node js app. i followed this url https://signoz.io/blog/nodejs-opensource-application-monitoring/

Can you try integrating console span exporter and check if spans are printed on terminal?

span are printing

then it’s issue with connection to otel collector

{"stack":"OTLPExporterError: Bad Request\n at IncomingMessage.res.on (/home/anil/workflow-camunda/smart-search/node_modules/@opentelemetry/otlp-exporter-base/build/src/platform/node/util.js7635)\n at manager.with (/home/anil/workflow-camunda/smart-search/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js5055)\n at AsyncHooksContextManager.with (/home/anil/workflow-camunda/smart-search/node_modules/@opentelemetry/context-async-hooks/build/src/AsyncHooksContextManager.js4223)\n at IncomingMessage.contextWrapper (/home/anil/workflow-camunda/smart-search/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js5032)\n at IncomingMessage.emit (events.js20315)\n at endReadableNT (_stream_readable.js114512)\n at process._tickCallback (internal/process/next_tick.js6319)","message":"Bad Request","name":"OTLPExporterError","data":"{\"code\":3,\"message\":\"unknown field \\\"scopeSpans\\\" in v1.ResourceSpans\"}","code":"400"}

wait checking

{ "name": "smart-search", "version": "0.0.0", "description": "Smart search using elastic search", "main": "index.js", "scripts": { "start": "node -r ./tracing.js index.js" }, "repository": { "type": "git", "url": "git+ssh://git@gitlab.com:company-framework/test.git" }, "keywords": [ "nodejs", "express", "elastic search", "mongodb" ], "author": "tester", "license": "ISC", "bugs": { "url": "https://gitlab.com/company-framework/test/issues" }, "homepage": "https://gitlab.com/company-framework/test#readme", "dependencies": { "@opentelemetry/api": "^1.4.0", "@opentelemetry/auto-instrumentations-node": "^0.36.0", "@opentelemetry/exporter-trace-otlp-http": "^0.35.0", "@opentelemetry/sdk-node": "^0.35.0", "apollo-server-express": "2.9.9", "body-parser": "1.19.0", "bookshelf-jsdoc-theme": "1.0.0", "compression": "1.7.3", "dot-object": "2.1.2", "elasticsearch": "15.4.1", "events": "3.1.0", "express": "4.16.4", "express-device": "0.4.2", "express-mongo-sanitize": "^2.0.0", "express-request-id": "1.4.1", "graphql": "^15.5.0", "helmet": "3.15.0", "jsonwebtoken": "^8.5.1", "minami": "1.2.3", "moment": "2.24.0", "mongoose": "5.4.11", "mongoose-auto-increment": "5.0.1", "morgan": "1.9.1", "namis": "1.0.3", "node-fetch": "2.6.0", "nodejs-tail": "1.1.0", "object-hash": "1.3.1", "pluralize": "7.0.0", "request": "2.88.0", "request-promise": "4.2.2", "role-acl": "4.4.0", "socket.io": "2.3.0", "swagger-jsdoc": "3.2.6", "swagger-ui-express": "4.0.2", "underscore": "1.9.1", "winston": "3.2.1", "xss-clean": "^0.1.1" }, "devDependencies": { "async": "2.6.1", "bytenode": "1.1.1", "chai": "4.2.0", "docdash": "1.0.2", "handlebars": "^4.5.0", "istanbul": "1.0.0-alpha.2", "jasmine": "3.3.1", "jasmine-reporters": "2.3.2", "javascript-obfuscator": "1.1.0", "jsdoc": "3.5.5", "nodemon": "2.0.2", "sanitation": "1.0.10", "supertest": "3.3.0", "terser-webpack-plugin": "2.0.1", "webpack": "4.39.3", "webpack-cli": "3.3.8", "webpack-node-externals": "1.7.2" } }

Is there any reason why you didn’t update to latest version of signoz?

signoz 10.2 is the latest version at that time of our first usage in our organization. we integrated most of our applications. now we are trying to integrate pending applications into the existing signoz version.

Are you using docker or k8s?

if i need to upgrade means then we need work on each application which we integrated already

@Anil Kumar Bandrapalli SigNoz upgrade won’t affect all your applications.

7-8 applications we already integrated. I will check locally and then try to upgrade it. is there any way to see compatible opentelemetry versions with signoz ?

This is might not be due to incompatibility with signoz, in some versions of otel exporter there are bugs but it’s possible that there is some bug in 0.36.0

ok