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

9
README.md
View file

@ -33,3 +33,12 @@ workload packaging remains outside this repo.
Run `python3 -m unittest discover -s tests -v` (Python 3.11+, no dependencies).
Live acceptance is tracked by RTEL-WP-0002-T04; local receipts are not external
operator delivery proof.
## Managed production package
[rapp-telemetry](../rapp-telemetry/README.md) packages Prometheus, Alertmanager
and Grafana for railiance01, with telemetry.coulomb.social as the intended
Grafana hostname. This repo retains Q2 contracts and rule meaning. The local
receiver and activity candidates are reference tooling; do not enable them as
a second production monitoring plane. Runtime deployment remains pending in
the package foundation workplan.

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.

9
workplans/RTEL-WP-0002-signal-contract.md
View file

@ -86,3 +86,12 @@ recurring-automations playbook. Native parser accepts both; 14 tests pass.
Recipient/channel clarification is pending. Runtime/profile and failure-domain
binding, off-host custody and actual notification acknowledgment remain unproven;
T04 remains wait, with no live schedule enabled.
Production package established September 6 at user direction: rapp-telemetry,
owned by this Q2 repo and declared against Master's normative schema. Selected
Prometheus/Alertmanager/Grafana via pinned kube-prometheus-stack; planned runtime
railiance01, Grafana telemetry.coulomb.social. RAPP-TELEMETRY-WP-0001-T03/T04 owns
package install, readiness and authenticated exposure. This T04 retains Q2's
exporter/rule mapping and actual delivery/absence acceptance. Existing SQLite
runtime and disabled activities are reference work, not the production service.
No package activation or Q2 delivery acceptance is claimed by repo creation.