-
Notifications
You must be signed in to change notification settings - Fork 569
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
Recommendations of the fencing event #87
Comments
I can add a unique event_id for each message such as: {
"command":"set",
"detect":"enter",
"key":"fleet",
"id":"bus1",
"event_id":"8aa68be86f92512a0d7c6804",
...
} Would this be helpful? |
what is it combined of event_id? |
Sorry for the delayed response. I think I understand now. So you would like to have your messages grouped by the "enter"/"exit" events? Perhaps something like this:
This is a good idea and I think that it's possible, but I'll need to dig a little deeper before making promises. |
Yes, it is. -:) |
Hi, @tidwall Note the same machine multiple tile38 process,tile38 can't produce the same group_id,can refer to mongodb objectid. |
I just pushed a build to master that groups with the key "group" and uses the BSON ObjectID format. Let me know if this works for you. |
That's great to hear. Let me know if there's anything you need. |
@tidwall , thanks! |
Hi, @tidwall
In the fencing event, each ENTER and EXIT are belong to the same group, you can consider adding a unique identity in the event of recognition?
This can be avoided, while many fences ENTER/EXIT after the information storage, sorted in order to know each Member of the Group
thanks!
huangpeizhi
The text was updated successfully, but these errors were encountered: