Virtual Tenants & RBAC

Create dedicated monitoring spaces with Role-Based Access Control for teams, geographies, and data types.

Key Capabilities

Multi-Tenancy Architecture

Create fully independent application spaces within TrackMe, each with its own configuration, entities, alerting rules, and monitoring scope — complete logical isolation within a single deployment.

Segregation of Duties

Three built-in roles — trackme_user (read-only), trackme_power (entity management), trackme_admin (content management) — enforce strict separation of responsibilities with full capability inheritance.

Functional Segmentation

Organize tenants by team, geography, technology stack, data sensitivity, or any business criteria. Security teams, network ops, and application owners each get their own dedicated space.

Component Isolation

Each tenant manages its own set of tracking components — data sources, data hosts, metric hosts, workload, fields quality — ensuring clear boundaries and no cross-tenant interference.

Tenant Health Monitoring

Continuously monitor the health, logic, and performance of each tenant. Track execution costs, resource consumption, and detect anomalies in tenant operations at a glance.

Dynamic Knowledge Objects

Automatic lifecycle management of knowledge objects — saved searches, lookups, macros — scoped to each tenant with full creation, update, and cleanup handled by TrackMe.

Scalable by Design

From a single tenant to dozens — scale horizontally as your monitoring needs grow. Each tenant adds minimal overhead while maintaining full feature parity.

Unified Administration

Administrators get a centralized view across all tenants while each team sees only their scope. Manage tenant lifecycle, components, and permissions from a single interface.

Local & Remote Deployments

Tenants can target the local Splunk environment or transparently monitor remote deployments, enabling centralized multi-site observability with proper access controls.