How to handle different traceIds for the same connection when implementing nodejs tcp server

[zerowise]

import * as net from 'net';
import agent, {ContextManager} from 'skywalking-backend-js';
import {SpanLayer} from "skywalking-backend-js/lib/proto/language-agent/Tracing_pb";
import {Component} from "skywalking-backend-js/lib/trace/Component";

agent.start({
    serviceName: 'experiment-sw-socket',
    collectorAddress: 'localhost:11800',
});

const handlerComponent = new Component(10000);
const server = net.createServer((socket) => {
    socket.write('hello world\n');
    // socket.end();

    socket.on("data", function () {
        const span = ContextManager.current.newEntrySpan(`socket`);
        span.component = handlerComponent;
        span.layer = SpanLayer.HTTP;
        span.peer = `${socket.remoteAddress}`;
        span.start();
        console.log(span.context.traceId())

        socket.write("\n1111\n", ()=>{
            span.stop()
        })
    })
});

server.listen(3000, () => {
    console.log('TCP Server is running on port 3000');
});
```

How to handle different traceIds for the same connection when implementing nodejs tcp server

[wu-sheng]

As I replied to you directly, you can't have that, because there is no header in TCP. Unless this is a private TCP for yourself, you need to propagate that.

ref doc https://skywalking.apache.org/docs/main/latest/en/api/x-process-propagation-headers-v3/

[zerowise]

Why can HTTP have different traceIDs each time it makes a request without headers, but TCP can't?

[wu-sheng]

Why do you keep asking me, but don't read what I said? What is point of that?

you can't have that, because there is no header in TCP. Unless this is a private TCP for yourself, you need to propagate that.

[zerowise]

When will nodejs version rpc framework plugins be supported, such as grpc