What is a BizMetry Template?¶

In BizMetry, a Template represents the telemetry blueprint or mold that defines what data is captured, how it is structured, and how it relates to your business context.
A Template determines what to capture and in what way, while setting guardrails to ensure only business-relevant and authorized data is collected.

Templates are the foundation of Business-Centric Observability, providing the semantic layer that ties together clients, resources, domains, and telemetry frames.

🧭 Concept Overview¶

A BizMetry Template encapsulates the rules, metadata, and taxonomy needed to capture telemetry aligned with your organization's operational and business goals.
It defines what business entities exist, what attributes can be measured, and how data flows across domains and clients.

Each Profile in BizMetry is associated with one Template — meaning the Profile's telemetry structure, frames, and business KPIs are driven by that Template.

⚙️ Template Components¶

A Template in BizMetry consists of several core configuration layers:

1. Client Types¶

Defines the types of clients or consumers of business resources (such as web applications, mobile apps, or AI agents).
Each Client Type groups clients with similar behavior, interaction models, or technical characteristics.

2. Resource Types¶

Defines the types or categories of resources (assets) that exist within a business domain.
A Resource Type is not an individual resource itself, but rather a taxonomic classification that allows multiple resources to be grouped under a shared conceptual type.

For example, a Resource Type called Order may group multiple Order instances or tables (such as sales_order, service_order, purchase_order) that share similar semantics or KPIs.
This abstraction enables telemetry and analytics to be applied consistently across all resources of the same type.

Each Resource Type can include: - A list of Attribute Types that describe the measurable properties common to all resources of that type.
- Metadata that defines how this type maps to concrete system entities or data sources.

3. Attribute Types¶

Specifies the individual metrics or properties captured for each Resource Type.
Attributes can be numeric, textual, Boolean, or enumerated values, and can include optional bounds or units.
Examples include order_id, price, token_usage, latency, or status.

4. Domains¶

Defines the business domains (bounded contexts) in which the resources operate.
Domains group resources with high functional cohesion — e.g., Inventory, Marketing, Orders, Trading, or Fleet Management.

5. Frame Types¶

Defines the structure of telemetry frames, describing how events and measurements are captured, transmitted, and visualized.
A Template can contain multiple Frame Types depending on the telemetry needs of the business or project.

🖼️ Template Structure Hierarchy¶

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

graph TD
    Template[Template]
    ClientTypes[Client Types]
    ResourceTypes[Resource Types]
    ResourceDomain[Resource Domain]
    AttributeTypes[Attribute Types]
    FrameTypes[Frame Types]

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

    ResourceTypes --> AttributeTypes

    style Template fill:#2196F3,stroke:#1565C0,stroke-width:3px,color:#fff
    style ClientTypes fill:#64B5F6,stroke:#1E88E5,stroke-width:2px,color:#000
    style ResourceTypes fill:#64B5F6,stroke:#1E88E5,stroke-width:2px,color:#000
    style ResourceDomain fill:#64B5F6,stroke:#1E88E5,stroke-width:2px,color:#000
    style FrameTypes fill:#64B5F6,stroke:#1E88E5,stroke-width:2px,color:#000
    style AttributeTypes fill:#90CAF9,stroke:#42A5F5,stroke-width:2px,color:#000

In BizMetry's Template model: - A Template defines the overall telemetry blueprint for a Profile. - Client Types categorize the consumers of business resources. - Resource Types define taxonomic classifications for business assets. - Resource Domain establishes the business context boundaries. - Frame Types specify how telemetry data is structured and transmitted. - Attribute Types describe the measurable properties of each Resource Type.

🧩 Defining Resource Types¶

When designing Resource Types, BizMetry supports two complementary approaches:

A. Manual Definition¶

Developers or architects can manually create each Resource Type and its associated Attribute Types, providing explicit control over naming, taxonomies, data types, and semantic relationships.

B. Database Introspection¶

BizMetry can automatically introspect existing databases within the customer's infrastructure, identifying table structures and mapping them to Resource Types.
Each discovered entity can then be linked to an appropriate Resource Type according to its schema or naming convention.
This ensures alignment between business telemetry definitions and actual data sources.

Supported databases: - MySQL
- PostgreSQL

🧠 Template Creation During Profile Setup¶

When creating a new Profile, BizMetry allows you to choose how its Template will be generated:

1. From an existing Profile
   Clones the Template structure of another profile for reuse and adaptation.

2. From an empty Template
   Creates a blank Template to define telemetry from scratch.

3. From a Master Template
   Initializes the Template from a pre-defined Master Template aligned with a business vertical or tech stack.

🏗️ Master Templates¶

BizMetry includes several Master Templates, each designed to fit common business domains and technology ecosystems.
Every Master Template is associated with:

• A language (e.g., English, Spanish, Japanese)
• A business vertical — such as Banking, Retail, Manufacturing, Technology, Telecom, or Healthcare
• A technology stack, such as Java + Spring Boot, Python + FastAPI, or Node.js + Express

When a Profile is created from a Master Template, it inherits these contextual configurations — ensuring semantic consistency across the telemetry layer.

💡 Why Templates Matter in BizMetry¶

Templates are the cornerstone of BizMetry's Telemetry Architecture, as they:

• Define what data is captured and why.
• Provide a clear taxonomy for grouping related business assets.
• Enforce structure and consistency across telemetry sources.
• Align business goals with technical observability.
• Enable standardized analytics across multiple profiles or environments.
• Ensure compliance with data governance policies by defining clear data boundaries.

By leveraging Templates, organizations can maintain a single source of truth for telemetry design — driving observability that's meaningful to the business, not just the infrastructure.

🧭 Conceptual Summary¶

🔗 Related Topics¶

• What is a BizMetry Client?
• What is a BizMetry Resource?
• What is a Business Domain?
• Understanding Telemetry Frames