TimeWarp.State.DevTools.Export 12.0.0-beta.17

TimeWarp.State.DevTools.Export

Dev-only exporter for the TimeWarp DevTools inspector. It copies completed activities from ActivitySource TimeWarp.State to POST /ingest/spans on the DevTools app. Other sources, including the .NET 11 framework sources Microsoft.AspNetCore, Microsoft.AspNetCore.Components, Microsoft.AspNetCore.Components.Server.Circuits, and Microsoft.AspNetCore.SignalR.Server, stay on the host's OTLP pipeline.

This package has no IState types. Referencing it does not register inspector states in StateCloneRegistry. Activity tags, including timewarp.state.store and timewarp.state.render, are copied onto the ingest item.

It is not an OpenTelemetry collector. The body is a small JSON document (name, tags, snapshot events, status, duration), not OTLP. Time-travel and other control operations are not in this package.

Register

WithTimeWarpStateDevTools on the Aspire AppHost sets TIMEWARP_STATE_DEVTOOLS_ENDPOINT. In the inspected app:

builder.Services.AddOpenTelemetry()
  .WithTracing(tracing =>
  {
    tracing.AddSource(TimeWarpStateTelemetry.ActivitySourceName);
    tracing.AddOtlpExporter();
    tracing.AddTimeWarpStateDevToolsExporter();
  });

When the variable is unset or blank, AddTimeWarpStateDevToolsExporter does nothing. When it is set to a value that is not an absolute URI, it throws InvalidOperationException.

A copied span with no timewarp.state.runtime tag is stamped server. A tag that is already present is left as it is. The browser exporter stamps wasm.

Spans whose timewarp.state.state_type is InspectorState, or whose timewarp.state.inspector tag is true, are dropped so the inspector cannot log itself.

Browser discovery

The browser does not see TIMEWARP_STATE_DEVTOOLS_ENDPOINT. On the server that hosts the WebAssembly app:

app.MapTimeWarpStateDevToolsClientConfig();

In Development that maps GET /_timewarp/state-devtools. A set variable returns { "endpoint": "<origin>" }. An unset variable returns 204. Other environments do not map the route. TimeWarp.State.DevTools.Wasm calls it. This package references the shared ASP.NET Core framework for that one route. It does not add a package dependency.

Manifest

The State source generator adds a manifest of each assembly's states and actions. Send it to DevTools once, at host start, so the inspector knows them before any span arrives:

builder.Services.AddTimeWarpStateDevToolsManifest(typeof(CounterState).Assembly);

It registers a hosted service that posts to POST /ingest/manifest. The body is { "Manifests": [ "<manifest json>", ... ] }. An assembly with no states adds nothing. When TIMEWARP_STATE_DEVTOOLS_ENDPOINT is unset, blank, or not an absolute URI, the call does nothing and raises no error. If DevTools is down, the post fails quietly and the app starts as usual. The post happens once and is not retried. If DevTools starts or restarts after the app, the Manifest tab stays empty until the app restarts.

This package now references TimeWarp.State to read StateManifestAttribute. Dispatching actions from DevTools is not implemented yet. The manifest carries the catalog names and parameters that a later dispatch channel will use.