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”, in which correlations are a given
The nodes contain a set of different metrics, and as seen in the table below, the Eyer structure replicates how Boomi expose the Atom JMX metrics. The table contain all metrics that Eyer is monitoring on an Atom.
Most of the metrics are described in System Monitoring with JMX from Boomi, but we added few more metrics (see the table below).
Node Name | Metric Name | GUID | Aggregation | Notes |
|---|---|---|---|---|
Operating System | ||||
System CPU Load | java.lang value | |||
Committed Virtual Memory Size | java.lang value | |||
Heap Memory Usage Committed | java.lang value | |||
Heap Memory Usage Used | ||||
Process CPU Load | java.lang value | |||
Total Physical Memory Size | java.lang value | |||
Execution Manager | ||||
Average Execution Queue Time | ||||
Average Execution Time | ||||
Local Running Workers Count | ||||
Queued Execution Estimated Count | ||||
Running Execution Estimated Count | ||||
Resource Manager | ||||
Atom In Bad State | com.boomi.container.services | |||
Deadlock Detected | com.boomi.container.services | |||
Low Memory | ||||
Out Of Memory | ||||
Too Many Open Files | com.boomi.container.services | |||
Scheduler | ||||
Executing Schedules Count | com.boomi.container.services | |||
Missed Schedules Count | com.boomi.container.services | |||
Schedule Count | ||||
Process Summary Reporting Service | ||||
Pending Execution Count | ||||
Pending Report Count | ||||
Pending Result Count | ||||
Message Queue Factory | ||||
Pending Message Count | com.boomi.container.services | |||
Config | ||||
Restarting | ||||
Status | It 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 Count | ||||
Queue Event track | ||||
Pending Upload Message Count | ||||
Message Poller Thread | ||||
Download Stats Connect Failure Count | Eyer does not use the cumulative value but the value of the difference between two subsequent data points | |||
Download Stats Delivered Message Count | Eyer does not use the cumulative value but the value of the difference between two subsequent data points | |||
Active MQ | ||||
Memory Percent Usage | ||||
