Virtana Platform
The Virtana Platform is a unified SaaS solution designed to simplify the migration, deployment, and ongoing optimization of hybrid and multi-cloud environments. The platform brings infrastructure visibility, analytics, and operational intelligence into a single environment so that you can manage complex IT ecosystems with greater clarity and control.
The platform delivers observability across both on-premises infrastructure and cloud environments, enabling your IT teams to monitor workloads whenever they run.
The Virtana Platform includes the following core modules:
Global View: A centralized dashboard for monitoring and managing performance across your applications and infrastructure.
Container Observability (CO): Deep visibility into applications running in Kubernetes-based environments.
Infrastructure Observability (IO): Monitoring for physical, virtual, and cloud-based infrastructure.
Service Observability: Full-stack monitoring for IT services, with dynamic service modeling and root-cause analysis.
Cloud Cost Management (CCM): Visibility and control over cloud spending, with rightsizing recommendations.
For detailed descriptions of each module, see What is the Virtana Platform.
Deployment architecture
The Virtana Platform uses a Kubernetes-based architecture that supports centralized management, distributed data collection, and unified observability across hybrid and multi-cloud environments. The architecture is organized into distinct layers that together provide authentication, monitoring, analytics, and automation. A central management cluster acts as the control plane, workload clusters run your applications, and Infrastructure Observability extends monitoring into your data centers.
Kubernetes-based deployment architecture. The management cluster contains Keycloak, the Global View control plane, Container Observability namespace groups, a StackStorm namespace, an Infrastructure Observability namespace, and a monitoring layer. Below it, three Kubernetes workload clusters each run a CO-South component, and two customer data centers are monitored by Infrastructure Observability.
Management cluster
The management Kubernetes cluster acts as the control plane for the entire solution. It hosts the Global View service, also called the control plane (CP), which provides the primary user interface and orchestration functions. Within the management cluster, the platform is segmented into namespaces for core capabilities.
The management cluster includes the following namespaces and services:
Container Observability (CO) namespaces contain the UI and data-plane components, shared services, and a set of Container Observability backends that scale horizontally—one backend for each connected workload cluster.
The Infrastructure Observability (IO) namespace ingests, processes, and analyzes infrastructure telemetry.
The
StackStormnamespace provides the automation and workflow engine that drives actions across the environment.Keycloak provides authentication for the platform.
The monitoring layer tracks the health of the platform itself.
Workload clusters
Beneath the management plane, multiple Kubernetes workload clusters run your applications. Each workload cluster includes a CO-South component that sits close to the workloads. CO-South collects cluster-level and application-level telemetry and sends it back to the Container Observability (CO) services in the management cluster. Otherwise, these workload clusters are standard Kubernetes environments with their own customer namespaces and services.
Customer data centers
The platform also extends into customer data centers, where Infrastructure Observability (IO) collectors and services monitor traditional infrastructure, including compute, storage, networking, and Hyperconverged Infrastructure (HCI) platforms. Telemetry from these on-premises environments flows into the Infrastructure Observability layer in the management cluster. Together, the Container Observability and Infrastructure Observability layers give the Virtana Platform a unified view across both containerized workloads and conventional infrastructure, all coordinated through a single centralized control plane.
Global View Multi‑Tenancy architecture
Global View supports multi-tenant deployments, so a single platform can serve multiple organizations while keeping each tenant's data separate. This design suits enterprises and managed service providers that manage several customers, departments, or business units on the same platform.
Global View multi-tenancy support includes:
Multiple tenants (organizations) per deployment.
An
ORG_ID(a UUID) for each tenant.Per-tenant endpoints for Container Observability (CO) and Infrastructure Observability (IO).
The following diagram shows how Global View keeps each tenant's data separate, even though all tenants share the same platform.
Multi-tenant data segregation diagram. Infrastructure Observability collectors from three tenant data centers push events to the CloudCAPI API gateway, which tags each event by tenant and routes it to tenant-tagged Kafka topics and services. Data is stored per tenant in SolrCloud (a collection per tenant), PostgreSQL (a schema per tenant), and VictoriaMetrics (a tenant_id label per series), and the UI service reads back only the requesting tenant's data.
Global View segregates tenant data through the following flow:
Push: Each tenant's Virtana Infrastructure Observability collectors send data to the shared API gateway (
CloudCAPI).Tag and sort: The gateway stamps each event with its tenant, then publishes it to the matching Kafka topic for alerts, inventory, or metrics.
Consume: Each service reads its own topic.
Store separately: Each service writes to its datastore, partitioned per tenant. SolrCloud keeps one collection per tenant, PostgreSQL keeps one schema per tenant, and VictoriaMetrics applies a
tenant_idlabel per tenant.View: The UI service reads back only the requesting tenant's slice of data.