Skip to main content

Synchronize External Business Traces

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.

Prerequisites​

  • The third-party system provides an HTTP API that ONE can access.
  • You have the synchronization URL and any network or authentication configuration required by the deployment.
  • Every topology and node has a stable, reusable unique ID.
  • To support drill-down from an interface topology to a service subgraph, you have matching interface and service topologies plus relationBindings data.

The endpoint must follow the External Synchronization API Reference.

1. Prepare the external endpoint​

  1. Provide a paginated endpoint that accepts POST requests.
  2. Accept page number, page size, topology ID, and topology name filters.
  3. Return pagination metadata and a results topology list.
  4. Return entities in nodes and relationships in edges.
  5. Add relationBindings when an interface node must open a service subgraph.

2. Configure the data source​

  1. Go to Insight → Business OB → Business Trace.
  2. Click External Data Synchronization.
  3. For first-time setup, click Data Source Configuration in the upper-right corner of the dialog.
  4. Enter the external synchronization URL and complete authentication as required by the deployment.
  5. Return to the Business Trace page.

3. Start synchronization​

  1. Click External Data Synchronization again.
  2. Review the message and click Confirm and Start Synchronization.
  3. Wait for synchronization to finish.

External data synchronization

warning

Do not close or refresh the page during synchronization. Run only one synchronization task per account at a time so the task state remains unambiguous.

4. Validate the result​

  1. Search for the target topology on the Business Trace page.
  2. Open it and verify node count, node names, and edge direction.
  3. Confirm that the topology update time matches the current synchronization.
  4. If you provided relationBindings, verify that an interface node opens the expected service subgraph.

Troubleshooting​

SymptomWhat to check
A topology does not appearCheck the response code, pagination fields, results, topology ID, and topology name.
Nodes appear without edgesVerify that every source and target in edges references a valid node in the same topology.
Interface-to-service drill-down failsVerify that interface and service topologies are returned as a pair and that relationBindings match.
Repeated synchronization creates duplicatesReturn the same stable unique ID for the same topology and node in every batch.
ONE cannot parse the responseCheck field types, required fields, and unsupported legacy formats in the API reference.

After synchronization succeeds, use Monitor and Investigate Business Traces with the imported data.