-
Notifications
You must be signed in to change notification settings - Fork 3
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
Reuse service id for patch #326
Conversation
Pull Request Test Coverage Report for Build 10729515210Details
💛 - Coveralls |
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.
For historical records: they might ask for timestamp information, ie, when the event happened. Just a note for future action....
That's a great point, updated to include a timestamp in seconds. It's like this now:
|
Relates to: #238, #235
Add a MongoDB collection "historical_connections" for saving the historical connections. Use service_id as key, a list of connection json as value. Example:
And enable using same service_id when doing PATCH