Proposal: Canton Observability Standard (COS)
RejectedPR- SIG
- needs-SIG
- Champion
- —
- Author org
- —
- Ask
- 1,600,000
Abstract
---
Milestones
| Title | Due date | Target | Amount (CC) |
|---|---|---|---|
| Specification Published and First Adopter Validated | — | At least one Canton operator team has reviewed the specification, provided written feedback incorporated into the final document, and confirmed the metric naming and label schema are legible in their existing stack without translation overhead. | 350,000 |
| Exporter Deployed and Emitting in a Live Environment | — | At least one Canton operator has deployed the reference Prometheus exporter or OpenTelemetry configuration against a real (non-sandbox) Canton node and confirmed that COS-specified metrics are appearing in their scrape target or trace backend with no manual remapping required. | 550,000 |
| Dashboards and Alerts Replacing at Least One Private Setup | — | At least one Canton operator team has imported the reference Grafana dashboard pack and Alertmanager alert rules into their production or staging environment, replacing or supplementing a previously private dashboard, and has confirmed the alerts are actionable with an acceptable false-positive rate. | 450,000 |
| Standard Adopted by Multiple Independent Teams and Publicly Released | — | At least three independent Canton operator or application teams have adopted some portion of COS (specification, exporter, dashboards, or alert rules) and the project has been publicly released with documented adoption evidence, so that future teams can start from a validated baseline rather than a blank slate. | 250,000 |
| Total | 1,600,000 | ||
Budget impact
- % of available
- 0.9%
- % if all RFV pass
- 0.9%
- Ask (CC)
- 1,600,000
Comments by org
2 comments · 0 orgs · last activity Apr 2, 2026
| Organisation | Comments |
|---|---|
| Unknown | 2 |