-
Notifications
You must be signed in to change notification settings - Fork 23
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
TimeStamped key for monitor values #132
Comments
Probably then a backend stream mapping to AggregatedKey with the relevant measures would be best? Or even just to use the aggregate key with equal start and end dates... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, It seems that monitors such as
android-application
andquestionnaire-completion-log
seem to useObservationKey
as the key for the topic, which would result in overriding the values over time on MongoDB. Can we useAggregatedKey
as the record key or aMonitorRecordKey
schema that hastimeRecorded
as a property?Any suggestions @blootsvoets , @yatharthranjan @kerzmaximilian ?
The text was updated successfully, but these errors were encountered: