You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bowire today reports nothing about its own operation — fine for a single-user laptop install, but the moment Multi-Tenant Phase B ships, operators of a shared instance need observability the same way they have it for every other service in the stack. The natural backend is whatever the org already runs (Prometheus / Loki / Tempo → Grafana); the natural protocol is OpenTelemetry. Optional, opt-in, off by default.
OpenTelemetry integration — AddOpenTelemetry().WithMetrics().WithTracing() in the standalone host, opt-in via a --telemetry CLI flag and the standard OTEL_* env vars.
Bowire-domain metric set — counters and histograms with stable names: bowire.invoke.duration, bowire.discover.count, bowire.recording.replay.frames, bowire.scan.findings, bowire.plugin.load.
Shared ActivitySource for embedded mode — Bowire's spans land in the host's existing OTel pipeline.
Reference Grafana dashboard — ship a dashboards/bowire-overview.json (Grafana 11+) under Bowire.Samples.
Privacy switch — --telemetry-strip-method-labels flag drops the high-cardinality service.method dimensions for shared-host deployments with regulated data.
BowireTelemetry static module: canonical ActivitySource + Meter on Kuestenlogik.Bowire with pre-declared instruments (bowire.invoke.count / .duration, bowire.discover.count, bowire.plugin.load, bowire.mock.requests).
BowireTelemetryOptions: { Enabled, StripMethodLabels } bound from Bowire:Telemetry.
AddBowireTelemetry(): registers the OTel SDK + ASP.NET / HTTP-client auto-instrumentation + OTLP exporter when Enabled. StripMethodLabels engages a MetricView that drops the high-cardinality service/method dims before export.
CLI flags: --telemetry and --telemetry-strip-method-labels mapped to the config keys.
BrowserUiHost wires AddBowireTelemetry automatically; embedded hosts that already run OTel can skip it and just AddSource/AddMeter the canonical name.
Invoke pilot: BowireInvokeEndpoints brackets protocol.InvokeAsync with an ActivitySource span + Counter.Add + Histogram.Record. Tags = protocol / service / method / outcome.
Open follow-ups for this issue:
Reference Grafana dashboard JSON in Bowire.Samples (dashboards/bowire-overview.json).
Activity
feat(telemetry): OpenTelemetry self-observability seam (#29 Phase 1)
thomas-stegemann commentedon Jun 4, 2026
Phase 1 landed.
Shipped:
Kuestenlogik.Bowirewith pre-declared instruments (bowire.invoke.count/.duration,bowire.discover.count,bowire.plugin.load,bowire.mock.requests).{ Enabled, StripMethodLabels }bound fromBowire:Telemetry.--telemetryand--telemetry-strip-method-labelsmapped to the config keys.Open follow-ups for this issue:
Phase 1 establishes the contract + the validation hot path. Further phases instrument more surfaces against the same Meter and ship the dashboard.
docs(dashboards): Grafana bowire-overview dashboard (Kuestenlogik/Bow…
fix(registry): don't abort an assembly's protocol scan on ctor-less t…
feat(bench): scheduled runs — persisted schedules + cron hosted servi…