Tagging chain for jsonrpsee log

[jasl]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

This is extracted from #11768

It's quite unclear that which chain get a new connection or disconnected

And, WS error: i/o error: Transport endpoint is not connected (os error 107); terminate connection 6 is the client force disconnect so I propose it move to WARN level and give a more clear log

khala-parachain node is based on polkadot-v0.9.27 Cumulus which still has this behavior, so it might not tracing bug

Steps to reproduce

No response

[bkchr]

@niklasad1 jsonrpsee is using its own thread pool or? If yes, the problem is that this is missing:

substrate/client/service/src/task_manager/mod.rs

Line 163 in 915f3c1

.in_current_span();

Basically forwarding of the current tracing span, that provides these information to which node the log belongs.

[niklasad1]

@niklasad1 jsonrpsee is using its own thread pool or? If yes, the problem is that this is missing:

No, it uses the tokio runtime from sc-cli /~https://github.com/paritytech/substrate/blob/master/client/rpc-servers/src/lib.rs#L159 (unless I have introduced a bug somewhere)

[bkchr]

@niklasad1 jsonrpsee is using its own thread pool or? If yes, the problem is that this is missing:

No, it uses the tokio runtime from sc-cli /~https://github.com/paritytech/substrate/blob/master/client/rpc-servers/src/lib.rs#L159 (unless I have introduced a bug somewhere)

Ahh yeah that looks right. However, we don't use the substrate task manager facilities.

We need to be able to pass some custom spawn function. So that we can instrument the future.