-
Notifications
You must be signed in to change notification settings - Fork 30
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
Message Tracing by metric log #34
base: master
Are you sure you want to change the base?
Message Tracing by metric log #34
Conversation
designs/message-trace/README.md
Outdated
- msg: message in process. For example, when join node send a concatenated message, use the message as an argument of `node.metric()`. | ||
- relatedMsgIds: array of ids of related messages. | ||
|
||
Note: we can put more complex information on the third argument of `node.metric()`. For example, we can make it a object which contains a array of message ids and a relation type such as `"isPartOf"`, `"splitInto"`, `"isDependsOn"`, etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to decide if it's going to be a more complex object from the start - it isn't something we can change later.
In the Join node scenario, which is the main scenario that requires this correlate
metric, I would suggest it looks like:
{ "join":["A", "B", "C" ...]}
That gives us room to introduce other correlate messages if they prove necessary.
Updated according to comment #34 (comment).
|
This design note proposes extension of metric log so that we can trace messages.
Part of message trace function can be implemented in 'Pluggable Message Routing', but runtime can't recognize a relationship between messages (e.g. in join node, runtime can't know which messages are combined into another message).