Metrics

Metrics are an abstraction layer for vehicle signals generated by physical sensors.
There is only one metric for each data field that a vehicle provides. For example, there is only one "Current Speed" metric, even if different sensors from different suppliers are used across our brands. CarNEO provides a continuously updated list of metrics you can use to specify the data collection.
A metric is static - It has a unique identifier (metric_id) and a static list of "data fields". This list describes the actual data that will be collected by the metric.
For example, the "Current Speed" metric has only one data field: speed.
The "Current Location" metric has two data fields: latitude and longitude.

Only for the metrics selected data fields will be collected from the vehicle.
No other data is collected by CarNEO.

Configurate Metrics

Via API, you can query all available metrics by calling:

GET /metrics

Vehicles have different capabilities based on the model and generation.
Insight into the metrics provided by individual vehicles are given by:

GET /vehicles/metrics_availability/{vin}

Sets metric availability for given vehicle can be done by:

PUT /vehicles/metrics_availability/{vin}

Roads to Rome

TODO: VWNWEBAPP-4114

It is a generic system that can be configured to extract data from different providers. The Roads to Rome concept provides the available metrics by fetching directly from your car's physical layer provider using
VIWI , SOME-IP and RSI.

The extraction is defined as a list of "extractors".
Each extractor has a "key", a "processor" and "options".
The "key" defines the method of how the data will be stored in the output, e.g. "URI".
The "processor" defines how the data is extracted from the input.
The "options" specify the parameters for the processor.

"extract":[{  
    "key": "URI"  
    "processor": "SELECT_BY_KEY"  
    "options":{ "SPEED"  
}  
}]