Skip to content

Self-telemetry + Grafana dashboards #29

Closed
Closed

Description

@thomas-stegemann

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.

Tracked in ROADMAP.md → Next.

Activity

  1. added this to the milestone on Jun 1, 2026
  2. moved this to Next up in Bowireon Jun 1, 2026
  3. modified the milestones: , v1.8 on Jun 3, 2026
  4. thomas-stegemann commented on Jun 4, 2026

    @thomas-stegemann
    MemberAuthor

    Phase 1 landed.

    Shipped:

    • 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).
    • Wider instrumentation across discover (BowireDiscoveryEndpoints), plugin-load (PluginManager / PluginPackageMap), mock (MockHandler bowire.mock.requests increment), recording paths.
    • Shared ActivitySource pattern note in docs/architecture/embedded.md so host integrators know how to attach.

    Phase 1 establishes the contract + the validation hot path. Further phases instrument more surfaces against the same Meter and ship the dashboard.

  5. moved this from Next up to Done in Bowireon Jun 5, 2026
  6. changed the issue type fromtoon Jun 7, 2026
  7. changed the issue type fromtoon Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status
      Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions