Skip to content

BizMetry Architecture

BizMetry is designed around a lightweight, distributed architecture that brings business-centric telemetry directly into your infrastructure. Rather than requiring data to be exported to an external system, BizMetry deploys intelligent agents close to your applications, capturing meaningful KPIs at the source and transmitting them to the central platform for analysis, alerting, and reporting.


Reference Architecture

At its core, BizMetry operates through three primary components that work together to collect, transport, and process business telemetry:

BizMetry Agents are lightweight processes that run within your on-premise or cloud environments. They collect telemetry from your business applications across different domains, implementing either manual or auto-instrumentation strategies. Agents pull telemetry definitions from the BizMetry Platform, then push captured metric points back — operating over a secured backbone using the RMTP/DMTP protocols.

BizMetry SDK can be seamlessly embedded into your application code, enabling development teams to generate and emit custom metrics programmatically following a low-code integration model. The SDK communicates directly with the co-located BizMetry Agent, abstracting the complexity of metric transmission from your application logic.

BizMetry Platform serves as the central intelligence layer. It stores the telemetry definitions (ASBOs, KPIs, Templates, Profiles), ingests metric points via reliable bulk ingestion, and exposes them through the Analytics Engine — powering real-time monitoring dashboards, smart reporting, KPI management, and business alerting.

A key concept in the architecture is the Capture Data Point (CDP) — strategically defined to ensure no critical KPIs are overlooked, all essential ASBOs and attributes are captured, and the resulting insights reflect accurate and complete KPI performance.

BizMetry Reference Architecture


Deployment Topologies

BizMetry supports two deployment topologies depending on whether your agents are deployed server-side alongside your APIs, or distributed at the client side. The choice of topology depends on your particular business use case.


Co-Located Topology

In the co-located topology, the BizMetry Agent is deployed within the same infrastructure as your business services and APIs — sitting close to the applications that receive requests from multiple clients.

This topology is the natural fit for the vast majority of traditional OLTP and three-tier architectures: web/mobile clients at the presentation tier, business services at the application tier, and databases at the persistence tier. BizMetry connects to this kind of architecture by intercepting inbound API calls at the gateway or service level, extracting business metrics without requiring changes to your core application logic.

How it works:

  • Clients (web, mobile, or system consumers) send requests to your API Gateway or business services.
  • The BizMetry Agent — co-located within the customer premises — intercepts those calls via the BizMetry Plugin at the API Gateway or directly from the BizMetry SDK embedded in your services.
  • The agent collects metric points from multiple clients under a single BizMetry Profile, making it straightforward to capture telemetry across all consumers from one centralized agent.
  • Metrics are transmitted securely over the backbone to the BizMetry Platform for ingestion and analysis.

Ideal for: ERP systems, OLTP business services, REST API platforms, microservices architectures, and any three-tier solution where all clients interact through a common server-side gateway.

Co-Located Topology

Co-Located Detailed Topology


Edge-Located Topology

In the Edge-Located Topology, BizMetry Agents are deployed on the client side, close to the source of data — typically remote or field devices that produce time-series data and transmit it back to a central location.

This topology is purpose-built for remote data sensing, IoT, and edge computing scenarios. Think of use cases like industrial sensor networks, fleet telemetry, remote monitoring stations, or any scenario where data originates outside the customer premises and needs to be ingested, processed, and analyzed at scale.

In this model, BizMetry acts as a modern, centralized, and scalable replacement for legacy data ingestion pipelines. Rather than building and maintaining a custom ingestion platform, organizations can delegate time-series data collection, analytics, alerting, and reporting directly to BizMetry — reducing operational complexity and cost significantly.

How it works:

  • Each distributed client (sensor device, remote node, edge application) has a BizMetry Agent deployed alongside it, using the BizMetry SDK for instrumentation.
  • Each client is assigned its own BizMetry Profile for isolation and independent management, allowing fine-grained control over what each remote node captures.
  • Agents intercept outbound calls for auto-instrumentation, transmitting metric data via RMTP over a secured backbone to the BizMetry Platform.
  • The platform ingests the time-series data in bulk, making it immediately available for analytics, dashboards, and alerting without custom development.

Key benefits over legacy ingestion platforms:

  • Modernization — replace difficult-to-scale, hard-to-maintain ingestion pipelines with a dynamic, reliable platform.
  • Cost reduction — typical remote sensing solutions involve tens to hundreds of clients with heavy compute and storage requirements. BizMetry handles this with minimal overhead.
  • Data flexibility — telemetry frames can be reconfigured as business requirements evolve, without code changes.
  • Centralized monitoring — all agents are monitored from a unified view, with configuration flexibility to accommodate varying client workloads.
  • Reduced time-to-market — a no-code/low-code approach means adapting to new ingestion requirements takes minutes, not weeks.

Ideal for: IoT and edge telemetry, remote data sensing, fleet management, distributed field device monitoring, and any scenario where data originates at geographically distributed client locations.

Edge-Located Topology


Summary

Co-Located Topology Edge-Located Topology
Agent placement Server-side, within customer premises Client-side, at remote locations
Client model Multiple clients share a single profile Each client has its own isolated profile
Instrumentation Intercepts inbound API/service calls Intercepts outbound calls from client
Primary use case OLTP, ERP, three-tier web/API platforms IoT, remote sensing, distributed devices
Data flow Clients → Gateway/Service → Agent → Platform Client Agent → Secured Backbone → Platform

Both topologies share the same BizMetry Platform at the core, ensuring consistent KPI governance, analytics, and real-time observability regardless of where your data originates.


Learn more about BizMetry at https://www.bizmetry.io or explore the documentation at https://docs.bizmetry.io.