Open fgalan opened 5 years ago
We have conducted some test with requests like that:
Dashboard -> LB -> IOTAM -> IOTA C++
Dasbhoard generated a correlator which is correctly printed by LB and IOTA C++ but not IOTAM. IOTAM shows corr=n/a in the traces.
corr=n/a
However it is able to propagate it (otherwise IOTA C++ wouldn't show it in the log) so maybe the problem is related only with the log printing logic.
Applies a similar solution like implemented in https://github.com/telefonicaid/iotagent-json/pull/478/ ?
Applies a similar solution like implemented in telefonicaid/iotagent-json#478 ?
Not sure but we could try...
We have conducted some test with requests like that:
Dashboard -> LB -> IOTAM -> IOTA C++
Dasbhoard generated a correlator which is correctly printed by LB and IOTA C++ but not IOTAM. IOTAM shows
corr=n/a
in the traces.However it is able to propagate it (otherwise IOTA C++ wouldn't show it in the log) so maybe the problem is related only with the log printing logic.