System Observability & Platform Operations

You can't run mission-critical commerce on a platform you can't observe and control. When something goes wrong at 2am—a cache issue, a failed job, a degraded API response—the difference between a ten-minute resolution and a two-hour outage is whether your team has the right visibility and controls in place before the incident, not after.

Virto ships observability as a native platform capability, not as an integration requirement. The System Operations console consolidates operational control into one documented interface. The OpenTelemetry module adds industry-standard OTLP observability across metrics, distributed tracing, and structured logging—and adds zero overhead when not configured. Both shipped in May 2026 as first releases.

• System Operations console: Health, Hangfire, Swagger, GraphQL, cache reset, platform restart, data import/export, and module load sequence—all consolidated into one documented control surface.
• OpenTelemetry module—OTLP: Zero overhead when not configured. Activates on demand for environments that require observability infrastructure.
• Distributed tracing: Full trace coverage across ASP.NET Core, HTTP Client, Hangfire, EF Core, Elasticsearch, and Redis—giving platform teams end-to-end request visibility across the full commerce stack.
• Metrics: ASP.NET Core, HTTP Client, Runtime, Process, EF Core, Elasticsearch, and Redis—the full set of infrastructure and application metrics needed for production monitoring.
• Structured logging: Serilog routed to OpenTelemetry via OTLP sink, with trace and span ID correlation for structured log analysis. Logs are tied to traces—not isolated entries.
• Amazon OpenSearch Service compatible: Observability data routable to AWS-managed infrastructure—no additional adapter required.
• Azure App Configuration: Centralized cloud-managed settings with Managed Identity and runtime refresh.
• Audit Logs: Compliance-grade change tracking across all platform entities—built in, not bolted on.
• Timestamp precision: Extended medium format (MM:DD:YYYY HH:MM:SS.fff) for log entries—millisecond precision for high-resolution diagnostics.
• Platform backup & restore: Page Builder, catalog, and platform data included in a unified backup pipeline—one operation covers the full platform state.

• Production readiness without external dependencies: Observability ships as a native platform capability. IT operations teams don't need to build monitoring infrastructure before going live—the tooling is already there.
• Zero overhead by default: OpenTelemetry activates only when configured. Environments that don't need observability infrastructure carry no performance cost for having the capability available.
• Faster incident resolution: Distributed tracing with trace and span ID correlation across the full stack means the time between "something is wrong" and "we know where" is measured in minutes, not hours.
• Compliance-grade audit trail: Change tracking across all platform entities is built in—reducing the effort and cost of compliance reporting in regulated industries.
• Centralized operational control: The System Operations console reduces the number of surfaces, tools, and undocumented admin pages platform teams have to navigate to maintain and diagnose the platform.
• Enterprise cloud integration: Azure App Configuration and Amazon OpenSearch Service compatibility mean Virto fits into existing enterprise cloud infrastructure without custom integration work.

• Platform and IT operations teams: A platform engineer needs to diagnose a degraded checkout experience during peak traffic. The System Operations console surfaces health status and Hangfire job queue in one place; OpenTelemetry distributed tracing pinpoints the EF Core query causing the latency spike. Resolution in minutes, not hours.
• Enterprise IT and compliance: A regulated enterprise needs a full audit trail of platform configuration changes for a quarterly compliance review. Audit Logs provide compliance-grade change tracking across all platform entities—exportable without custom tooling.
• Multi-environment cloud deployments: A platform team running separate staging and production environments on Azure needs to push a configuration change without a restart. Azure App Configuration with runtime refresh applies the change across environments without downtime.
• AWS-infrastructure organizations: An enterprise running observability on Amazon OpenSearch Service routes Virto's OpenTelemetry output directly to their existing AWS-managed infrastructure—no additional adapter, no custom integration.