What is a Telemetry Profile?

In BizMetry, a Telemetry Profile is a top-level abstraction that groups together all business telemetry configurations related to a specific project within your organization's IT ecosystem.

A profile represents the operational boundary for observability — defining what to monitor, where to monitor it, and how metrics are captured and analyzed across different environments, clients, and resources.

🧭 Concept Overview¶

A Telemetry Profile provides a unified configuration context that binds all components involved in BizMetry's business-centric observability model.
It defines the telemetry scope for a given project or business unit, acting as the bridge between your business operations and the BizMetry Platform.

Profiles make it possible to segment and isolate telemetry configurations by product, department, or environment — enabling independent management, visualization, and governance of metrics and KPIs.

🧩 Profile Composition¶

Each Telemetry Profile in BizMetry is associated with the following elements:

Component	Description
🧱 Environments	One or more runtime environments (e.g., Development, QA, Production) where your business applications are deployed.
⚙️ Agents	BizMetry agents deployed across your infrastructure to collect, process, and transmit telemetry data in real time.
🧩 Telemetry Template	The model defining what to observe — including business domains, resources, attributes, and frame types to be captured.
👥 Clients	The consumers of your business resources (applications, APIs, devices, or AI agents) that generate measurable interactions.
🏷️ Resources (Assets)	The business entities or assets (ASBOs) that are being monitored and linked to key performance indicators (KPIs).
🖼️ Telemetry Frame	Defines the attributes to be captured as part of business instrumentation (either automatic or manual). Multiple frames can be defined depending on needs. Each telemetry frame represents the smallest unit of telemetry capture by the platform and agents.

💡 Each Profile acts as a self-contained observability space, mapping clients and assets within a shared telemetry configuration that can be deployed, measured, and managed consistently.

🧠 Organizational Context¶

In BizMetry's hierarchy:

A BizMetry Account can contain multiple Profiles.
Each Profile corresponds to a specific project, product, or operational area.
Profiles define the telemetry scope and manage their own templates, agents, and environments.

This hierarchical model allows large organizations to manage observability at scale, with clear ownership and isolation between projects.

🧱 Example Scenarios¶

Profile Name	Purpose	Environments	Telemetry Template
Retail AI Assistants	Observability for AI-based customer support agents in retail stores.	`dev`, `qa`, `prod`	AI Chat Template
Fleet Operations	Monitoring fleet telematics and logistics workflows.	`staging`, `production`	Logistics Telemetry Template
Banking Digital Services	Observability for online banking and transaction systems.	`prod`	Finance Transaction Template

🧩 Each profile independently tracks KPIs, agents, and resources — enabling specialized observability per business domain.

🧮 Key Benefits¶

Defining distinct profiles in BizMetry allows organizations to:

Segment telemetry configurations by business project or unit.
Simplify administration of environments, templates, and agents.
Control scope and granularity of business observability.
Scale independently, managing different telemetry lifecycles per profile.
Enable contextual KPI analysis, linking metrics directly to the right assets and clients.

🖼️ BizMetry Telemetry Profile Hierarchy¶

The diagram below illustrates how Telemetry Profiles fit within the broader BizMetry ecosystem.
It shows how a profile binds together environments, agents, and telemetry frames, all derived from a shared template that defines what to capture and how.

In BizMetry's telemetry model: - A Profile belongs to a single Account.
- Each Profile manages one or more Environments where its systems run.
- Each Environment deploys one or more Agents responsible for capturing telemetry.
- Agents collect Telemetry Frames, which contain Resources (assets) and Attributes (metrics).
- Frames are transmitted via RMTP to the BizMetry platform for consolidation and analysis.

🖼️ Profile Structure Hierarchy¶

The following diagram illustrates the hierarchical structure of a BizMetry Profile and its core components:

graph TD
    Account[Account]
    Profile[Profile]
    Environments[Environments]
    Agent[Agent]
    Template[Template]
    ClientTypes[Client Types]
    ResourceTypes[Resource Types]
    ResourceDomain[Resource Domain]
    AttributeTypes[Attribute Types]
    FrameTypes[Frame Types]
    Clients[Clients]
    Resources[Resources]

    Account --> Profile
    Profile --> Environments
    Profile --> Template
    Profile --> Clients
    Profile --> Resources

    Environments --> Agent

    Template --> ClientTypes
    Template --> ResourceTypes
    Template --> ResourceDomain
    Template --> FrameTypes

    ResourceTypes --> AttributeTypes

🧭 Summary¶

A BizMetry Telemetry Profile is the highest administrative unit below an account.
It defines what is being observed, where telemetry data originates, and how it's collected across your business infrastructure.

Groups all telemetry configurations for a project.
Associates templates, environments, agents, clients, and resources.
Provides logical isolation between different business or product areas.
Forms the backbone of BizMetry's scalable observability model.