martin/production-analytics
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Persist material consumption snapshots

Browse Source
This commit is contained in:
admin
2026-09-05 11:35:25 +02:00
parent 7c029759f5
commit ae13c3c35a
9 changed files with 303 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/roadmap.md
+5 -3
View File
@@ -24,9 +24,11 @@ Runtime options select the polling interval, state directory (default: ignored
`data/state/material/`), and existing secrets-file handling. Only one writer may
poll each machine/order state key.
The runner exposes no Grafana/TimescaleDB metric yet and does not complete the
MVP. Grafana-oriented derived-total persistence/exposure is the next milestone,
with the TimescaleDB persistence foundation below. No HTTP endpoints, application
The runner now persists cumulative material-consumption snapshots for Grafana in
PostgreSQL using `db/schema.sql`. JSON remains the restart checkpoint; PostgreSQL
stores derived time-series snapshots only. No Timescale-specific features are used.
A new order may first appear with a non-zero total after initial sample integration.
Grafana dashboard validation remains pending. No HTTP endpoints, application
containers, daemonization, or schedulers have been added.
Detect the currently active Production Run and production order, continuously