Telemetry

FabrCore 2.0 · Release and package availability

These guides track the current 2.0 source. Stable 2.0.0 publication is pending; package commands show the release target. Until it is published, follow the source quick start or use a matching available prerelease set. Release migration · Runtime modes

Telemetry

FabrCore includes OpenTelemetry instrumentation across host grains, SDK agent execution, WebSocket ingress, and HTTP API activity.

Orleans 10.3 migration

FabrCore 2.0 uses Orleans 10.3.1. Update external dashboards and trace queries for these renamed RPC tags:

Previous	Current
`rpc.system`	`rpc.system.name`
`rpc.service`	`orleans.rpc.service`
`rpc.orleans.target_id`	`orleans.rpc.target_id`
`rpc.orleans.source_id`	`orleans.rpc.source_id`

rpc.method now contains <interface>/<method>. Upgrading the runtime does not update your external dashboards automatically.

OpenTelemetry Setup

builder.Services.AddOpenTelemetry()
    .WithTracing(tracing => tracing
        .AddSource("FabrCore.Sdk.*")
        .AddSource("FabrCore.Host.*")
        .AddSource("FabrCore.Host.PrincipalGrain"))
    .WithMetrics(metrics => metrics
        .AddMeter("FabrCore.Sdk.*")
        .AddMeter("FabrCore.Host.*")
        .AddMeter("FabrCore.Host.PrincipalGrain"));

Metrics

Principal grain metrics use the fabrcore.principal.* naming family. Agent grain metrics continue to use fabrcore.agent.*. HTTP/API clients should be observed with normal application HTTP instrumentation plus FabrCore Host traces.

Distributed Tracing

FabrCore propagates TraceId, SpanId, and ParentSpanId across messages and events. Verifiable execution signs the same causal graph when evidence recording is enabled.

Cloud monitoring and diagnostic usage

The 2.0 cloud query APIs expose retained monitor records and health without continuous cluster export. SQL buffering is optional and does not await persistence in the recording path. Source identities, unavailable hosts, retention boundaries and capture gaps qualify the view.

Diagnostic model use is attributed to _admin, the admin execution category, actor, target and session. Keep those costs distinguishable from production work. Provider-lifetime token/cost summaries are not an all-time cluster billing ledger. Diagnostic transcripts remain accessible through administration sessions only; existing OpenTelemetry and audit behavior is preserved.