55 lines
1.5 KiB
Markdown
55 lines
1.5 KiB
Markdown
# Runtime tachograph Esper scope processing
|
|
|
|
This document is kept for compatibility with earlier patches.
|
|
|
|
The preferred endpoint is now the generic Runtime Event Processing endpoint:
|
|
|
|
```http
|
|
POST /api/eventhub/runtime-processing/event-processing
|
|
```
|
|
|
|
Use the tachograph profile key:
|
|
|
|
```text
|
|
tachograph-driver-esper-v1
|
|
```
|
|
|
|
The old endpoint remains available as an adapter:
|
|
|
|
```http
|
|
POST /api/eventhub/runtime-processing/tachograph/esper-processing
|
|
```
|
|
|
|
It delegates to the same profile infrastructure used by the generic endpoint. See:
|
|
|
|
```text
|
|
docs/runtime-event-processing.md
|
|
```
|
|
|
|
Vehicle-only evidence is now attached through the same common runtime event-processing profile. The old compatibility endpoint maps:
|
|
|
|
```json
|
|
{
|
|
"expandVehicleEvents": true,
|
|
"vehicleExpansionPaddingMinutes": 15
|
|
}
|
|
```
|
|
|
|
to the generic profile behavior:
|
|
|
|
```json
|
|
{
|
|
"parameters": {
|
|
"attachVehicleOnlyEvents": true,
|
|
"vehicleEvidencePaddingMinutes": 15
|
|
}
|
|
}
|
|
```
|
|
|
|
Attachment is temporal: a vehicle-only event must match a reconstructed driver vehicle-usage interval and occur inside the interval plus configured padding.
|
|
|
|
|
|
## Debugging vehicle evidence attachment
|
|
|
|
Prefer the generic `/api/eventhub/runtime-processing/event-processing` endpoint with `partitioning.includeDebug=true` or `parameters.includePartitionDebug=true`. The compatibility response type has `partitionDebugByDriver`, but the generic endpoint is the preferred way to enable debug output explicitly. The generic response exposes debug data under `partitionResults[*].metadata.partitionDebug`.
|