Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TimeStamped key for monitor values #132

Open
nivemaham opened this issue Jul 19, 2018 · 1 comment
Open

TimeStamped key for monitor values #132

nivemaham opened this issue Jul 19, 2018 · 1 comment

Comments

@nivemaham
Copy link
Contributor

Currently, It seems that monitors such as android-application and questionnaire-completion-log seem to use ObservationKey as the key for the topic, which would result in overriding the values over time on MongoDB. Can we use AggregatedKey as the record key or a MonitorRecordKey schema that has timeRecorded as a property?
Any suggestions @blootsvoets , @yatharthranjan @kerzmaximilian ?
@nivemaham nivemaham mentioned this issue Jul 26, 2018
Merged
@blootsvoets
Copy link
Contributor

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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@blootsvoets @nivemaham