We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
Applies a similar solution like implemented in telefonicaid/iotagent-json#478 ?
Sorry, something went wrong.
Not sure but we could try...
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: