Local versus Remote
For Humainary, the goal is to encourage as much as possible the analytical processing of observations at the source of event emittance and in the moment of the situation. To propagate assessments, not data.
Whereas for OpenTelemetry, the focus is moving as much data as possible along delineated pipelines onto a remote endpoint.
The approach taken with Humainary is to enable the effective and efficient design, development, and deployment of Observability signaling circuitry that operates primarily locally by default but can operate in a remote or simulated mode.
We envisage engineers being able to rapidly innovate in designing and developing novel instruments for measuring, sensing, observing, analyzing, reasoning, and reacting to behavior and structural changes as they happen.
Humainary offers out-of-the-box channels of communication and coordination across a diverse set of instrument libraries that operate in near-real-time and within the local process space of a (micro)service.
Remote communication occurs only when data has been transformed into information at higher-order levels and scales.
Pipes and Points
The OpenTelemetry approach is akin to connecting a network cable to an outbound port and letting packets pass without inspection.
This proposed standard is driven by application performance vendors and ex-Google engineers looking to solve a 20-plus-year-old problem of tag-and-trace of requests across processes by reinventing the application response measurement (ARM) standard.