Support Multiple Sources in Metrics API - Sessions and Aggregates #190
Description
Is your feature request related to a problem? Please describe.
- The current architecture supports mainly a single data_source_device or data_source_operator for both types of metrics: sessions and aggregates. If two demand sources like sensor and camera are linked to the same curb zone, and these metrics are requested for it, there is no parameter in the schema that indicates the data source device type or operator.
Describe the solution you'd like:
- Including fields of data_source_type and/or data_source_operator_id in both types of metrics.
- Including the data_source_type as a query parameter in sessions and aggregates endpoints. This can allow clients to pull data only of their preferred provider and not have to filter additional sources in the post-processing.
Is this a breaking change
- Yes, new columns need to be added to the schema and query parameters. May need another version
Impacted Spec. For which spec is this feature being requested?
- Sessions and Aggregates
Describe alternatives you've considered
- A temporary alternative to implement multiple sources in the current version may be to choose and inform the default source for aggregates and show only data for it. Or include only the query parameter but the query response would have only the current columns.
- The data sources available and operators can be found in the event/status endpoint.
- This would be temporary solution but does not efficiently support multiple demand data sources.