Kitepipe AtomWatch

Supported OS Linux Mac OS

marketplace
Integration version1.4.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

AtomWatch by Kitepipe is an Agent-based integration that collects metrics from Boomi processes, cluster nodes, and related infrastructure to inform both Datadog and Boomi customers about the health of the integration.

This integration contains 7 dashboards, 17 custom metrics, and 16 monitors that report on Boomi execution statistics, cluster status, JMX monitoring, and infrastructure health. These metrics are available to Datadog and Boomi customers for extended time-trending analysis (over the standard of 30 days for Boomi Process Reporting availability).

Datadog customers who purchase AtomWatch must manage the Boomi Java Runtime in either an Atom or Molecule configuration. Kitepipe includes a one hour set-up and configuration session with the initial 14 Day Free Trial.

About Kitepipe

Kitepipe is a Boomi Platinum Implementation Partner, and is the premier Boomi integration development team in North America. Kitepipe was founded in 2011 in response to the need for a Boomi-focused services team that could deliver all the promises of this powerful integration platform.

Today, the Kitepipe team of certified Boomi on-shore developers help dozens of Boomi customers quickly achieve business value with the industry-leading Boomi integration platform.

The Datadog service AtomWatch is a new offering from Kitepipe with a focus on Boomi managed services in AWS. Kitepipe is the leader in a number of integration areas, verticals, and domains, including AWS migrations of Boomi processes, AWS managed Boomi, Biotech vertical solutions built on Boomi, NetSuite, SAP, Coupa, Workday, and HRIS, Data Mart/BI, and more endpoints.

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

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 <BRACKETED_VALUES> with appropriate values for your setup:

Note: For more information about the conf.d location on different operating systems, see Agent configuration directory.

---
logs:
  - type: file
    path: <BOOMI_INSTALL_DIR>/logs/*.container.<BOOMI_NODE_ID>.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:

    logs_enabled: true

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 <BRACKETED_VALUES> with appropriate values for your setup.

    ---
logs:
  - type: file
    path: <BOOMI_INSTALL_DIR>/logs/*.shared_http_server.<BOOMI_NODE_ID>.log
    service: BoomiHTTP
    source: kitepipe-boomi
    log_processing_rules:
    - type: exclude_at_match
      name: exclude_healthcheck
      pattern: _admin/status

  2. In the datadog.yaml file, ensure the following line is present and uncommented:

    logs_enabled: true

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. You can build your own monitors to inspect the unfiltered AuditLog records.

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

Metrics

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

For support or feature requests, reach out to AtomWatch through the following channel:

Kitepipe 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 Kitepipe 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

Additional helpful documentation, links, and articles:

Installation and Setup v1.4.0DOCUMENTATION more more Monitor your Boomi integrations with Kitepipe's offering in the Datadog MarketplaceBLOG more more