54 lines
1.2 KiB
Markdown
54 lines
1.2 KiB
Markdown
# Runtime tachograph Esper scope processing
|
|
|
|
This document is kept for compatibility. The preferred architecture is now the common Runtime Processing execution model.
|
|
|
|
Preferred endpoint:
|
|
|
|
```http
|
|
POST /api/eventhub/runtime-processing/executions
|
|
```
|
|
|
|
Use:
|
|
|
|
```json
|
|
{
|
|
"processingPlanKey": "driver-working-time-v1"
|
|
}
|
|
```
|
|
|
|
Legacy compatibility endpoint:
|
|
|
|
```http
|
|
POST /api/eventhub/runtime-processing/tachograph/esper-processing
|
|
```
|
|
|
|
still exists and delegates through the common runtime processing infrastructure.
|
|
|
|
Legacy profile endpoint:
|
|
|
|
```http
|
|
POST /api/eventhub/runtime-processing/event-processing
|
|
```
|
|
|
|
with:
|
|
|
|
```json
|
|
{
|
|
"profileKey": "tachograph-driver-esper-v1"
|
|
}
|
|
```
|
|
|
|
also remains available, but new clients should use `processingPlanKey` and `/executions`.
|
|
|
|
The current `driver-working-time-v1` plan uses these modules:
|
|
|
|
```text
|
|
event-to-activity-intervals
|
|
event-to-vehicle-usage-intervals
|
|
vehicle-evidence-attachment
|
|
support-evidence-normalization
|
|
driving-derived-projections
|
|
```
|
|
|
|
It can load runtime events from multiple sources and sessions, partition them by driver, attach vehicle-only evidence by vehicle/time overlap, normalize support evidence, and run the existing tachograph Esper/Java processing chain per driver partition.
|