-
Notifications
You must be signed in to change notification settings - Fork 378
Telemetry cannot be used for parachain and for relaychain at the same time #149
Comments
Partial fix has been merged to substrate: paritytech/substrate#6666 This will allow enabling the telemetry for the parachain but not for the relaychain OR: for the relaychain but not for the parachain. (This fix is not on cumulus yet, need to update substrate) |
I looked at the code and I don't think there is a way to distinguish between the telemetry of the para chain and the relay chain as logs are global and everything is sent to the telemetry worker (relay and para chain logs). There are 2 ways we can go from there:
There might a a third way: we remove the use of set_global_logger and we pass a logger instance everywhere and adapt the code accordingly. It's probably as massive as it sounds. |
Ah I just found #154 So we should take option 3 and there is a feature for that. Cool! |
This one |
Related to #19 : I guess if we have a specific logger instance per node we can easily improve the prefixing |
Logging without a singleton is a pain in the ass. |
* update rust-toolchain: nightly-2022-11-14 * bump deps: compilation starts * launch runtime compiles * encointer-runtime compiles * bump runtime-spec versions * node builds
This is a limitation in substrate. The telemetry must be initialized only once.
Related to paritytech/substrate#6666 (this is not a fix as this doesn't allow using the telemetry on the parachain and the relaychain at the same time)
The text was updated successfully, but these errors were encountered: