Skip to content
New issue

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

Correlator id not correctly logged? #168

Open
fgalan opened this issue Jan 11, 2019 · 2 comments
Open

Correlator id not correctly logged? #168

fgalan opened this issue Jan 11, 2019 · 2 comments
Labels

Comments

@fgalan
Copy link
Member

fgalan commented Jan 11, 2019

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.

@fgalan fgalan added the bug label Jan 11, 2019
@AlvaroVega
Copy link
Member

Applies a similar solution like implemented in telefonicaid/iotagent-json#478 ?

@fgalan
Copy link
Member Author

fgalan commented Jun 16, 2020

Applies a similar solution like implemented in telefonicaid/iotagent-json#478 ?

Not sure but we could try...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants