Skip to main content

Boomi data collector structure

The data coming from the Influx Telegraf monitoring Atoms are structured into nodes and metrics.

Nodes are logical entities that contain metrics that we already know “work together,” and correlations are given.

The nodes contain a set of different metrics, and as seen in the table below, the Eyer structure replicates how Boomi exposes the Atom JMX metrics. The table contains all metrics that Eyer is monitoring on an Atom.

Most metrics we monitor are described in System Monitoring with JMX from Boomi, but there are a few more (see the table below).

Node NameMetric NameGUIDAggregationNotes
Operating System
System CPU Load5523ee20-2af2-4b8e-8390-3d2cb4410018avgjava.lang value
Committed Virtual Memory Size2ce746c5-1ee3-45d1-b23f-bae56bc5d51aavgjava.lang value
Heap Memory Usage Committed324b4bb1-cf29-4dce-9539-479d8b3bb41bavgjava.lang value
Heap Memory Usage Used631bf72c-0b1a-4f74-929c-d60360a71896avg
Process CPU Loada59df24a-e9ec-4c4c-a087-ea1375d4b9c7avgjava.lang value
Total Physical Memory Size8edca7a9-b9aa-487b-a68c-ddaf18393a3davgjava.lang value
Execution Manager
Average Execution Queue Timeb0ea4cd2-823f-4539-be9a-6a3ef3365964avg
Average Execution Time50060171-414b-4cbd-8534-5b0d9338c86bavg
Local Running Workers Count27dad857-3cc3-4daf-8671-114678579f04avg
Queued Execution Estimated Count80c9b07c-d11a-4857-a6b4-323a300bd9efavg
Running Execution Estimated Count0dee40ce-19bf-4717-ac9e-1465f8c62cf3avg
Resource Manager
Atom In Bad State8e838d01-69fa-4b48-8e6d-9fd0d82d80c7maxcom.boomi.container.services
Deadlock Detected5318feea-b009-4da0-a94a-98bdfddad45emaxcom.boomi.container.services
Low Memoryab4af37f-f63b-4ca0-9145-e020534460e2max
Out Of Memoryd991d4f8-042a-4e35-bec2-698bce56af0emax
Too Many Open Files8cd82c74-7a2d-4b31-b41e-a8d176bc3a49maxcom.boomi.container.services
Scheduler
Executing Schedules Count593729c7-b3ca-463a-a00d-e788fc381262avgcom.boomi.container.services
Missed Schedules Count2fd40a14-59f3-45bc-af46-816670a5da2amaxcom.boomi.container.services
Schedule Count572639db-ec74-4527-9e59-3810c8fee227avg
Process Summary Reporting Service
Pending Execution Counteaba890f-0c62-40e8-9c64-777cff3b7aceavg
Pending Report Count60c74b9d-03d3-4185-b98c-e1f61f3cc9fdavg
Pending Result Countf9546e5b-ec20-45cc-a710-5637ff1a7966avg
Message Queue Factory
Pending Message Count0482bb04-f2a1-407e-a4f3-21dad77ef1adavgcom.boomi.container.services
Config
Restartingf6fce7f1-1af9-4298-9db2-5193c12bccedmax
Status3f42f923-ca99-4317-97b8-2e9c48cb903dmaxIt is mapped from a string to a boolean, where RUNNING is mapped to 0 and all the others are mapped to one
Queue Acknowledgement track
Pending Upload Message Count69f10518-7033-4026-b42b-b93473b610deavg
Message Poller Thread
Download Stats Connect Failure Countdd5c666c-35fc-4ce2-b3c1-b146ef302fa0sumEyer does not use the cumulative value but the value of the difference between two subsequent data points
Download Stats Delivered Message Countb4a2c6ab-0ae5-489d-a964-36984eca3dd2sumEyer does not use the cumulative value but the value of the difference between two subsequent data points
Active MQ
Memory Percent Usageavg

This is what the metrics look like in VisualVM when it's connected to an Atom process. Boomi structure