đī¸ Introduction
Business Observability organizes systems, services, interfaces, and technical components along critical business paths. It brings metrics, alerts, logs, and traces into one business view so you can assess health, follow dependencies to anomalous nodes, and verify recovery.
đī¸ Create traces
The goal of a business trace is not to reproduce every technical dependency. Model the nodes, relationships, and health signals that affect a critical business outcome so the path is both monitorable and actionable.
đī¸ Implementation steps
Use these steps to build the first usable business trace. When complete, the Business Trace page shows the target business state and key metrics, and the topology provides access to node details.
đī¸ Best practices
The long-term usefulness of a business trace depends on stable scope, complete data, and consistent health criteria. Use these recommendations after completing the initial implementation.
đī¸ Business trace investigation
Use the Business Trace page to identify flows that need attention during routine monitoring. When an anomaly appears, follow the same business path to locate affected nodes, correlate observability data, and verify recovery.
đī¸ External data synchronization
When a third-party system owns the business topology, use external synchronization to import business traces, nodes, edges, and interface-to-service drill-down relationships into ONE. You can then use the same Business Observability monitoring and investigation workflows.
đī¸ External synchronization API
This reference is for developers and integration engineers implementing an external synchronization endpoint. It defines pagination, topology models, node and edge constraints, and interface-to-service drill-down bindings. For the setup workflow, complete Synchronize External Business Traces first.