Boomi is an Integration Platform as a Service (iPaaS) used by thousands of organizations to connect applications, data, and workflows across cloud and on-premises environments. Business-critical processes, from order fulfillment pipelines to customer data synchronization, depend on Boomi Atoms and Molecules running reliably. Yet until Boomi introduced native OpenTelemetry (OTel) support for its integration runtimes in September 2025, gaining deep Boomi observability and understanding how runtimes perform in production was a significant challenge for operations and business teams.
Adding native OTel support to Boomi was a welcome step forward. Teams can now export traces, logs, and metrics from their Boomi Atoms by using the industry-standard OpenTelemetry Protocol (OTLP), without installing third-party agents or custom plugins. However, one hurdle remains: OTel provides collection and transport but does not provide a platform to store data and run analysis. Turning that telemetry data into actionable insights requires a backend that can store, correlate, and query the data.
In this post, we’ll show how you can instrument and monitor Boomi Atoms and Molecules with OTel and Datadog to gain end-to-end visibility into your integration processes, including distributed traces, natively correlated logs, inferred service dependencies, and database query insights. Specifically, we’ll cover:
