coulomb/railiance-telemetry
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Bind Q2 production architecture to rapp-telemetry

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
tegwick 2026-09-06 20:27:30 +02:00
parent a32c0f1541
commit ae37a78e31
3 changed files with 29 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/signal-contract.md
View file

@ -99,3 +99,14 @@ executor/profile, immutable bundle, upstream platform report command, state
location and notification channel. No resolver, live schedule or second host
cron has been introduced. Strict profile-enforcing environments need the accepted
profile binding before registration; none is invented in these candidates.
## Production architecture decision — 2026-09-06
The user directed Master-compliant package establishment on railiance01.
`rapp-telemetry` now owns the maintained kube-prometheus-stack release:
Prometheus, Alertmanager and Grafana. Grafana's intended hostname is
telemetry.coulomb.social. The local SQLite receiver/runtime remains a reference
implementation. Do not activate its candidate activity definitions as a parallel
production monitoring plane. Q2 now needs a reviewed Prometheus exporter/rule
mapping preserving the existing state semantics, and actual Alertmanager delivery
acceptance. Package runtime/admission is tracked by RAPP-TELEMETRY-WP-0001.