Skip to content

Conversation

@k-toumura
Copy link
Contributor

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).

- 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.
Copy link
Member

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.

@k-toumura
Copy link
Contributor Author

Updated according to comment #34 (comment).

  • use complex object for third argument of node.metric().
  • update a figure of correlation log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants