-
Notifications
You must be signed in to change notification settings - Fork 265
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
Improvements in Orion logs system #3694
Comments
The following old-INFO traces will remain at the end:
which I think is good enough. |
Regarding
It will be implemented only for non-initial notifications (i.e. it will be implemented for notifications that are caused by a entity creation/update). In the case of initical notification only only notification exists associated to the causing operation (which is subscription creation/update) so it is pointless to add a counter. |
Feedback from a review with @manucarrace @mrutid and @AlvaroVega
Subscription used for the test:
Update used for the test:
|
Check implementation with large payloads. I think we have a "LINE TOO LONG" guard in traces that can hide log trace completely and we should see how we can deal with that. |
Regarding:
Now INFO at startup is as follows:
|
With regards to query forwarding reference execution using cases/0787_cprs_full_functional_v2/ngsiv2_query_five_different_cprs_in_one_query.test
Note they are NGSIv1 payload (it's and old test) but, for the point of view of this functionality, it doesn't make any difference. |
Ideally, we should introduce two CLI switches to deal with this:
|
PR #3696 |
The following modifications has to be done in the Orion Context Broker logs system:
; notif=n
where "n" is an autoincremental counter (1, 2, 3, etc.) local to the e2e flow that caused the nofiication. I mean, if a given update hascorr=10405986-e4e7-4ee4-95c7-bfec5282e3a4
and three notifications are generated as consecuence of that update, then notifications will have the following correlators:corr=10405986-e4e7-4ee4-95c7-bfec5282e3a4; notif=1
corr=10405986-e4e7-4ee4-95c7-bfec5282e3a4; notif=2
corr=10405986-e4e7-4ee4-95c7-bfec5282e3a4; notif=3
The text was updated successfully, but these errors were encountered: