Skip to content

Commit 93e347a

Browse files
committed
Reframe driver as Cozystack adopters, not a named client
Drop the specific client reference (hidora); the motivation is request-level visibility requested by Cozystack adopters generally. Signed-off-by: Alexey Artamonov <[email protected]>
1 parent cecf8b5 commit 93e347a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • design-proposals/distributed-tracing

‎design-proposals/distributed-tracing/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In scope: a traces backend (per-tenant and, as an opt-in, shared-central), an OT
2525
- **Collection agents:** `packages/system/monitoring-agents` (fluent-bit, vmagent) — the *deployment* pattern the collector borrows, but note the traffic model differs (see [§2](#2-multitenancy-and-network-model-the-core-decision)).
2626
- **Network policy:** `packages/apps/tenant/templates/networkpolicy.yaml` — the Cilium tenant-isolation policies this design must live within.
2727
- **Prior art in-repo:** Harbor exposes an internal, app-local trace config (`packages/system/harbor/charts/harbor/values.yaml`, provider `jaeger`/`otel`); it is not a platform backend. This proposal supersedes ad-hoc per-app trace endpoints with a shared destination.
28-
- **Driver:** requested by a client (hidora) who needs request-level visibility across managed DBaaS and messaging services.
28+
- **Driver:** requested by adopters of Cozystack who need request-level visibility across managed DBaaS and messaging services.
2929

3030
## Context
3131

0 commit comments

Comments
 (0)