The operating problem
Proxy metrics alone cannot explain policy decisions, customer impact, configuration propagation, or business usage—and careless labels can leak data or explode cardinality.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- OpenTelemetry traces and bounded metrics
- Redacted traffic inspection
- Golden signals and deployment correlation
- Tenant-safe usage and SLO views
What exists today
Privacy-minimized Envoy request events and traffic summaries are persisted and tenant-scoped alongside readiness, audit, and deployment history. OpenTelemetry export, distributed tracing, SLOs, anomaly detection, and alerting are not shipped.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.