--- title: Atturra AtomWatch description: Monitor Boomi processes and infrastructure breadcrumbs: Docs > Integrations > Atturra AtomWatch --- # Atturra AtomWatch Supported OS marketplaceIntegration version1.6.0 Enhanced Process Reporting lets you look back more than 30 days and filter by more fields, with wildcards.See long-running processes at a glance and receive alerts with anomaly detection.Extensive infrastructure monitoring including CPU, RAM, Disk, Network.Cluster monitoring that exceeds Boomi's published recommendations.Toplists and graphs of errored Boomi processes.Supports JMX Monitoring. ## Overview{% #overview %} AtomWatch offers a comprehensive solution for real-time performance tracking of Boomi Atoms, Molecules, and Private Clouds. AtomWatch supports Boomi operating on the Linux OS only, a best practice for the Boomi runtime in on-premises, cloud, or hybrid customer environments. **Key capabilities**: - **Real-Time JVM Monitoring**: Detailed visibility into Boomi Node performance through Heap and Thread monitoring. - **Process-Level Metrics**: Track and analyze resource loads at the individual process level, allowing for targeted diagnostics. - **Actionable Insights**: Diagnose performance issues and optimize Boomi runtimes with unparalleled data precision. This integration includes 8 dashboards, 17 custom metrics, and 16 monitors that report on Boomi execution statistics, cluster status, JMX monitoring, and infrastructure health. AtomWatch allows Boomi developers and teams to gain deep insights into the health and efficiency of their Boomi integrations, enabling them to maintain smooth operations, prevent downtimes, and improve overall system performance. ### About Atturra{% #about-atturra %} Atturra is a Boomi Platinum Partner with an expert global team who acquired Kitepipe in 2025. Now as Atturra North America, we are a full-service provider for full-platform process development, offering a global 24/7 support experience and a Boomi hosting, monitoring, and management solution. The experience of helping over 700 clients in ANZ and Asia, along with US operations since 2011, makes us a reliable partner adhering to global standards with local expertise. ### Log Collection{% #log-collection %} This integration makes API calls to the Boomi Platform on your behalf, retrieving execution records and sending them to Datadog as logs. It also optionally monitors in-progress executions and JVM telemetry through JMX, sending this information to Datadog as logs. You can see which Boomi processes are running in which JVMs, along with associated metrics such as memory usage, garbage collection, thread count, and more. #### Container logs{% #container-logs %} To configure the Datadog Agent to ship Boomi container logs to your Datadog account, perform these steps on each molecule node: 1. Create the following file at `/etc/datadog-agent/conf.d/BoomiContainerLog.d/conf.yaml`, replacing `` with appropriate values for your setup: **Note**: For more information about the `conf.d` location on different operating systems, see [Agent configuration directory](https://docs.datadoghq.com/agent/configuration/agent-configuration-files.md#agent-configuration-directory). ```yaml --- logs: - type: file path: /logs/*.container..log service: BoomiContainerLog source: kitepipe-boomi log_processing_rules: - type: multi_line name: multi_line_rule pattern: \w+ \d+, \d+ \d+:\d+:\d+ (AM|PM) ``` 1. In the `datadog.yaml` file, ensure the following line is present and uncommented: ```yaml logs_enabled: true ``` #### HTTP logs:{% #http-logs %} To configure the Datadog Agent to ship Boomi HTTP logs to your Datadog account, perform these steps on each molecule node: 1. Create the following file at `/etc/datadog-agent/conf.d/BoomiHTTPLog.d/conf.yaml` (or equivalent Windows location), replacing `` with appropriate values for your setup. ```yaml --- logs: - type: file path: /logs/*.shared_http_server..log service: BoomiHTTP source: kitepipe-boomi log_processing_rules: - type: exclude_at_match name: exclude_healthcheck pattern: _admin/status ``` 1. In the `datadog.yaml file`, ensure the following line is present and uncommented: ```yaml logs_enabled: true ``` ### Events{% #events %} This integration retrieves AuditLog records from the Boomi API, and sends them to Datadog as events. The events are visible in filtered form in the Boomi Workload Monitoring Dashboard or in the [Events Explorer](https://app.datadoghq.com/event/explorer). You can build your own monitors to inspect the unfiltered AuditLog records. ### Metrics{% #metrics %} | | | | | **kitepipe.atomwatch.execution.status**(count) | Tracks how many Boomi executions have occurred as well as their status. | | **kitepipe.atomwatch.execution.measure.inboundDocumentCount**(gauge) | Boomi ExecutionRecord "inboundDocumentCount" value. | | **kitepipe.atomwatch.execution.measure.inboundErrorDocumentCount**(gauge) | Boomi ExecutionRecord "inboundErrorDocumentCount" value. | | **kitepipe.atomwatch.execution.measure.outboundDocumentCount**(gauge) | Boomi ExecutionRecord "outboundDocumentCount" value. | | **kitepipe.atomwatch.execution.measure.duration**(gauge) | Boomi ExecutionRecord "executionDuration" value.*Shown as millisecond* | | **kitepipe.atomwatch.execution.measure.inboundDocumentSize**(gauge) | Boomi ExecutionRecord "inboundDocumentSize" value.*Shown as byte* | | **kitepipe.atomwatch.execution.measure.outboundDocumentSize**(gauge) | Boomi ExecutionRecord "outboundDocumentSize" value.*Shown as byte* | | **kitepipe.atomwatch.execution.measure.inProgressExecutionDuration**(gauge) | Records how many minutes a Boomi process has been running, if it is still in progress at the moment that the Datadog integration ran.*Shown as minute* | | **kitepipe.atomwatch.boomi\_api\_calls\_attempted**(count) | How many Boomi API calls of any type have been made. | | **kitepipe.atomwatch.view\_file\_exist**(gauge) | Value of 1 if view file exists. | | **kitepipe.atomwatch.view\_file\_age\_seconds**(gauge) | Time in seconds since last update of the view file.*Shown as second* | | **kitepipe.atomwatch.view\_file\_problem**(gauge) | Tracks occurrence of Boomi cluster View File problems. Value of 1 if view file contents indicate cluster problem. | | **kitepipe.atomwatch.integration\_completed**(gauge) | Tracks successful completion of a AtomWatch integration run. Value of 1 if integration completed successfully. | | **kitepipe.atomwatch.jvm.cpu\_time\_ms**(gauge) | JVM CPU time consumed | | **kitepipe.atomwatch.jvm.heap.memory**(gauge) | JVM heap memory | | **kitepipe.atomwatch.jvm.runtime\_out\_of\_memory**(gauge) | JVM out of memory condition | | **kitepipe.atomwatch.jvm.runtime\_low\_memory**(gauge) | JVM low memory condition | ## Data Collected{% #data-collected %} ### Metrics{% #metrics-1 %} ### Service Checks{% #service-checks %} **kitepipe.atomwatch.skipped\_molecule\_view\_file** Returns OK if Agent has skipped checking a molecule view file during latest run. *Statuses: ok* **kitepipe.atomwatch.skipped\_api\_gateway\_view\_file** Returns OK if Agent has skipped checking an API Gateway view file during latest run. *Statuses: ok* **kitepipe.atomwatch.checked\_molecule\_view\_file** Returns OK if Agent checked a molecule view file during latest run. Returns CRITICAL if unable to complete the check. *Statuses: ok, critical* **kitepipe.atomwatch.checked\_api\_gateway\_view\_file** Returns OK if Agent checked an API Gateway view file during latest run. Returns CRITICAL if unable to complete the check. *Statuses: ok, critical* **kitepipe.atomwatch.config\_validated** Returns OK if Agent was able to validate configuration. *Statuses: ok* **kitepipe.atomwatch.datetime\_range\_set\_up** Returns OK if Agent was able to set up datetime range for making Boomi API calls. *Statuses: ok* **kitepipe.atomwatch.boomi\_api\_calls\_permitted** Returns OK if Boomi API calls will be attempted (and not skipped) on this run. *Statuses: ok* **kitepipe.atomwatch.skipping\_boomi\_api\_calls** Returns OK if Agent declined to attempt Boomi API calls because it was too soon since last API call. *Statuses: ok* **kitepipe.atomwatch.completed** Returns OK if Agent has completed all AtomWatch checks. Returns CRITICAL if unable to complete successfully and WARNING if there were failures querying Boomi Platform API. *Statuses: ok, warning, critical* **kitepipe.atomwatch.persisted\_end\_datetime** Returns OK if AtomWatch persisted the last used end datetime. *Statuses: ok* **kitepipe.atomwatch.queried\_boomi\_executions** Returns OK if Agent called the Boomi ExecutionRecord API on this run. Returns CRITICAL if tried and failed to call API. *Statuses: ok, critical* **kitepipe.atomwatch.found\_boomi\_executions** Returns OK if Agent queried Boomi ExecutionRecord API and found records in target date range. *Statuses: ok* **kitepipe.atomwatch.submitted\_execution\_metrics** Returns OK if Agent submitted metrics on this run, derived from Boomi ExecutionRecord API calls. *Statuses: ok* **kitepipe.atomwatch.submitted\_execution\_logs** Returns OK if Agent was able to submit Boomi execution-record logs (not process logs) to Datadog. *Statuses: ok* **kitepipe.atomwatch.queried\_boomi\_auditlogs** Returns OK if Agent called the Boomi AuditLog API on this run. Returns CRITICAL if tried and failed to call API. *Statuses: ok, critical* **kitepipe.atomwatch.found\_boomi\_auditlogs** Returns OK if Agent queried the Boomi AuditLog API and found records in target date range. *Statuses: ok* **kitepipe.atomwatch.submitted\_auditlog\_events** Returns OK if Agent submitted events on this run, derived from Boomi AuditLog API calls. *Statuses: ok* **kitepipe.atomwatch.queried\_boomi\_events** Returns OK if Agent called the Boomi Events API on this run. Returns CRITICAL if tried and failed to call API. *Statuses: ok, critical* **kitepipe.atomwatch.found\_boomi\_events** Returns OK if Agent queried the Boomi Events API and found records in target date range. *Statuses: ok* **kitepipe.atomwatch.submitted\_boomievent\_events** Returns OK if Agent submitted events on this run, derived from Boomi Event API calls. *Statuses: ok* **kitepipe.atomwatch.used\_default\_last\_end\_datetime** Returns warning if Agent could not parse Last End Datetime from file and had to use default value. *Statuses: warning* **kitepipe.atomwatch.longrunning\_execution\_failed\_metric\_submission** Returns warning if Agent could not submit metrics showing the name and duration of a long-running Boomi process. *Statuses: warning* **kitepipe.atomwatch.boomi\_daemon\_running** Returns OK if Boomi daemon is running. Returns Critical if verified that Boomi daemon is NOT running. *Statuses: ok, critical* **kitepipe.atomwatch.runtime\_reported\_online** Returns OK if Boomi datacenter reports the runtime (atom, molecule, or API gateway) as online; else returns Critical *Statuses: ok, critical* **kitepipe.atomwatch.jmx\_monitoring** Returns OK for success. Returns Critical for failure *Statuses: ok, critical* ## Support{% #support %} For support or feature requests, reach out to AtomWatch through the following channel: - Email: [Kitepipe.atomwatchsupport@atturra.com](mailto:Kitepipe.atomwatchsupport@atturra.com) Atturra support hours for AtomWatch are designated during the business hours of 9AM to 3PM across US and Canadian time zones. AtomWatch troubleshooting requests will be answered within 24 to 48 hours from the notification receipt to the AtomWatch email alias. For best response results, include the customer name, Boomi configuration, and a brief description of the event or troubleshooting question. Enhanced support programs are available from Atturra upon request. This application is made available through the Marketplace and is supported by a Datadog Technology Partner. Click Here to purchase this application. ## Further Reading{% #further-reading %} - [Monitor your Boomi integrations with Kitepipe's offering in the Datadog Marketplace](https://www.datadoghq.com/blog/kitepipe-datadog-marketplace/)