Skip to content

Runtime Observability and Introspection Boundaries ​

Self-built logging, MetricRegistry, span/trace, log/metric push, and some management queries exist. No dedicated Profiler, OpenTelemetry SDK, or OTLP exporter is integrated. Design proposals do not establish deployed functionality.

Existing implementation ​

CapabilitySource and boundary
Local loggingmodules/core/log; see logging for output and push.
MetricsMetricRegistry in modules/core/metrics; not CPU/stack sampling.
Span/tracemodules/net/linktrace and RpcTrace in remoteentity; self-built context/emission rather than OTel integration.
Push/managementmodules/net/metricspush and apps/admin aggregation/HTTP metrics; deployment requires separate acceptance.
Crash captureSee crash capture; dumps are not a live Profiler.

Observation across roles ​

loginServer records authentication, directory registration/expiry, and ownership changes. gateway records connections, sessions, and Base/cell routes. Base records base gameplay, settlement, and pending storage results. World records registration, topology, placement, and transfer decisions. cell records Cells, entities, Instances, ticks, and state handoff. database records storage admission, durable outcomes, failure, and retry. machined records local process lifecycle.

Correlate player IDs, Base/World/Cell/executor identities, session/route versions, transfer/settlement IDs, and process/business generations. Machine addresses do not identify player ownership. Do not log credentials or database passwords.

Diagnostic ownership ​

Obtain runtime snapshots at their owning execution boundaries rather than traversing mutating simulation/profile containers from management threads. Administrative changes still require authentication, authorization, and business intents; debug access must not bypass Base/World/cell/database authority.

Structured queries and Watcher-style trees are diagnostic design directions, not an implemented unified Watcher Tree or complete introspection platform. Profiler, OTel, and external collectors remain requirement-driven without new game process roles.

Acceptance ​

Validate process liveness, readiness, admission, execution, and durable results separately. Observe Base associations, scene transfer, and update phases; a trace, restart, or successful log does not establish seamless upgrades. Validate sampling cost, exporter backpressure, and failure handling when an actual integration exists.

Track implementation only in root todo.md. See architecture and update boundaries.

Released under the MIT License